Mer/Documentation/Getting your package included

Latest revision as of 10:46, 22 September 2010

Mer is back : Please visit http://www.merproject.org to learn more about this news.

Make sure it compiles after getting your build dependancies, dpkg-buildpackage.
Ideally test dpkg-buildpackage -S -us -uc, dpkg-buildpackage -b -us -uc, and dpkg-buildpackage -B (some packages may not build any arch-dep packages, so that's OK. Microdocument it on Jaiku.)
bzr export source package name lp:~yourusername/m-r/source package name (gives you a checked out version, without metadata)
cd source package name
dpkg-buildpackage -S -us -uc, to generate a source package
Upload the resulting source package (*.changes, *.tar.gz, possibly *.diff.gz) to your ~/incoming on trac.tspre.org.
ssh yourlogin@trac.tspre.org /import-new-packages

(This will add the source package to repository, and complain otherwise.)

You need access to merbuilder & repository upload for the following, ask Stskeeps on Jaiku/IRC for this.
Builder is at http://trac.tspre.org:8000
Follow instructions, and submit job.

@@ Line 4: / Line 4: @@
 * Ideally test <code>dpkg-buildpackage -S -us -uc</code>, <code>dpkg-buildpackage -b -us -uc</code>, and <code>dpkg-buildpackage -B</code> (some packages may not build any arch-dep packages, so that's OK. Microdocument it on Jaiku.)
 * <code>bzr export ''source package name'' lp:~''yourusername''/m-r/''source package name''</code> (gives you a checked out version, without metadata)
-* <code>cd ''<source package name>''</code>
+* <code>cd ''source package name''</code>
 * <code>dpkg-buildpackage -S -us -uc</code>, to generate a source package
 * Upload the resulting source package (<code>*.changes</code>, <code>*.tar.gz</code>, possibly <code>*.diff.gz</code>) to your <code>~/incoming</code> on trac.tspre.org.