Mer/Documentation/Common Packages

Help bringing a package up to date

 * Make yourself a launchpad.net account, and upload your SSH keys and install Bazaar.
 * Grab the source package the Mer package is based on, and the new one from fremantle alpha, extract them. diff -ruN them, and save the diff (from now on patchname).
 * Typical files to avoid patching (you can delete them in the resulting patch):
 * .in files
 * configure
 * (feel free to add more to the list)
 * bzr branch 
 * cd into the checked out directory
 * apply patch from before (patch -p1 < patchname probably, you can patch -p1 --dry-run < patchname to test run the patch), fix it if it doesn't apply cleanly (watch out for configure and autoconf generated things)
 * bzr add any added files (avoid .rej and .orig, bzr status is a good tool.)
 * dch -m -i, and add your personal log message. Name the version, mer version + 1.
 * bzr commit -m "your personal log message"
 * bzr push lp:~yourusername/m-r/packagename
 * Ideally, bzr export lp:~yourusername/m-r/packagename, cd and try to dpkg-buildpackage -b it.
 * Point us to the branch and we'll put the branch in the repository and build it.

Most patches apply cleanly, though, you will most likely see patch failed in debian/changelog, is fairly easy to fix, just add the items from .rej without the +'s in the front and add an according version above it using dch.

Typical package repositories

 * Diablo versions: http://repository.maemo.org/pool/diablo/free/
 * Pre-alpha1: http://repository.maemo.org/pool/maemo5.0prealpha1/free/
 * Pre-alpha2: http://repository.maemo.org/pool/maemo5.0prealpha2/free/
 * Alpha: http://repository.maemo.org/pool/maemo5.0alpha/free/
 * Stage SVN: https://stage.maemo.org/viewcvs.cgi/projects/haf/trunk/, https://stage.maemo.org/svn/maemo/projects/haf/trunk/
 * Stage SVN: https://stage.maemo.org/viewcvs.cgi/projects/haf/tags/, https://stage.maemo.org/svn/maemo/projects/haf/tags/