Editing Mer/Documentation/Getting your package included

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.

Learn more about Contributing to the wiki.

* Make sure it compiles after getting your build dependancies, <code>dpkg-buildpackage</code>.
* 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>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.
* <code>ssh ''yourlogin''@trac.tspre.org /import-new-packages</code>

(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. Or refer on Jaiku to the source package and some may pick it up
* On http://jaiku.com/channel/merbuilder , write "build <SOURCE PACKAGE NAME>=<package version>"
* You can also save the builder some resources if it's an arch-indep package and do "build-x86 <SOURCE PACKAGE NAME>=<package version>"
* You can make a specific rebuild using build-armel-sb (build in scratchbox), 
* Monitor progress at same page (RSS: http://jaiku.com/channel/merbuilder/feed/rss )
* An LP player notes that it has picked up a package for building at a certain builder
* A toast means it baked properly on this architecture. And is uploaded to repository.
* A heart means it built properly on all architectures. And is uploaded to the repository
* A bomb means it failed to build on an architecture.
* A shopping wagon means it has noticed your build request and queued it.
* A straightjacket means that it failed to build on Scratchbox and needed to be built natively. Note this in [[Mer/Documentation/Straightjacket _Packages|Straightjacket packages]] when this happens. means there's a bug in SDK.)

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!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Ambox (view source) (semi-protected)
Template:Mer (view source) (semi-protected)

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

Personal tools

Navigation

Views

Editing Mer/Documentation/Getting your package included

@@ Line 11: / Line 11: @@
 (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.
+* You need access to merbuilder & repository upload for the following, ask Stskeeps on Jaiku/IRC for this. Or refer on Jaiku to the source package and some may pick it up
-* Builder is at http://trac.tspre.org:8000
+* On http://jaiku.com/channel/merbuilder , write "build <SOURCE PACKAGE NAME>=<package version>"
-* Follow instructions, and submit job.
+* You can also save the builder some resources if it's an arch-indep package and do "build-x86 <SOURCE PACKAGE NAME>=<package version>"
+* You can make a specific rebuild using build-armel-sb (build in scratchbox),
+* Monitor progress at same page (RSS: http://jaiku.com/channel/merbuilder/feed/rss )
+* An LP player notes that it has picked up a package for building at a certain builder
+* A toast means it baked properly on this architecture. And is uploaded to repository.
+* A heart means it built properly on all architectures. And is uploaded to the repository
+* A bomb means it failed to build on an architecture.
+* A shopping wagon means it has noticed your build request and queued it.
+* A straightjacket means that it failed to build on Scratchbox and needed to be built natively. Note this in [[Mer/Documentation/Straightjacket _Packages|Straightjacket packages]] when this happens. means there's a bug in SDK.)