Editing Mer/Documentation/Common Packages

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 3: Line 3:
== Help bringing a package up to date ==
== Help bringing a package up to date ==
-
* Make yourself a launchpad.net account, upload your SSH keys, and install Bazaar.
+
* Make yourself a launchpad.net account, and upload your SSH keys and install Bazaar.
-
* Grab the source package that Mer package is based on, and the new one from the Fremantle alpha, extract them. <code>diff -ruN</code> them, and save the diff (from now on ''patchname'').
+
* 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):
* Typical files to avoid patching (you can delete them in the resulting patch):
-
** <code>.in</code> files
+
** .in files
-
** <code>configure</code>
+
** configure
-
** ''(feel free to add more to the list)''
+
** (feel free to add more to the list)
-
* <code>bzr branch <lp:''something listed in table below''></code>
+
* bzr branch <lp:something listed in table below>
-
* <code>cd</code> into the checked out directory
+
* cd into the checked out directory
-
* Apply the patch from before (<code>patch -p1 < ''patchname''</code> probably, you can <code>patch -p1 --dry-run < ''patchname''</code> to test run the patch), fix it if it doesn't apply cleanly (watch out for <code>configure</code> and <code>autoconf</code> generated things)
+
* 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)
-
* <code>bzr add</code> any added files (avoid <code>.rej</code> and <code>.orig</code>, <code>bzr status</code> is a good tool)
+
* bzr add any added files (avoid .rej and .orig, bzr status is a good tool.)
-
*<code> dch -m -i</code>, and add your personal log message. Name the version, Mer version + 1.
+
* dch -m -i , and add your personal log message. Name the version, mer version + 1.
-
* <code>bzr commit -m "your personal log message"</code>
+
* bzr commit -m "your personal log message"
-
* <code>bzr push lp:~''yourusername''/m-r/''packagename''</code>
+
* bzr push lp:~yourusername/m-r/packagename
-
* Ideally, <code>bzr export ''<some dir>'' lp:~''yourusername''/m-r/''packagename''</code>, <code>cd ''<some dir>''</code> and try to <code>dpkg-buildpackage -b</code> it.
+
* Ideally, bzr export <some dir> lp:~yourusername/m-r/packagename , cd <some dir> and try to dpkg-buildpackage -b it.
* Point us to the branch and we'll put the branch in the repository and build 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 <code>debian/changelog</code>, is fairly easy to fix, just add the items from <code>.rej</code> without the <code>+</code>'s in the front and add an according version above it using <code>dch</code>.
+
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 ==
== Typical package repositories ==

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://wiki.maemo.org/Mer/Documentation/Common_Packages"