Mer/Documentation/Getting your package included
Line 11: Line 11:
(This will add the source package to repository, and complain otherwise)
(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
+
* You need access to merbuilder & repository upload for the following, ask Stskeeps on Jaiku/IRC for this.  
-
* On http://jaiku.com/channel/merbuilder , write "build <SOURCE PACKAGE NAME>=<package version>"
+
* Builder is at http://trac.tspre.org:8000
-
* You can also save the builder some resources if it's an arch-indep package and do "build-x86 <SOURCE PACKAGE NAME>=<package version>"
+
* Follow instructions, and submit job.
-
* 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.)
+

Revision as of 08:45, 10 April 2009

Getting your package included in the Repository

  • Make sure it compiles after getting your build dependancies, dpkg-buildpackage.
  • Ideally test both dpkg-buildpackage -S -us -uc, dpkg-buildpackage -b -us -uc, dpkg-buildpackage -B (some packages may not build any arch-dep packages, so that's ok. Microdocument it on Jaiku.)
  • bzr export

    Invalid language.

    You need to specify a language like this: <source lang="html4strict">...</source>

    Supported languages for syntax highlighting:

    abap, actionscript, actionscript3, ada, apache, applescript, apt_sources, asm, asp, autoit, avisynth, bash, basic4gl, bf, bibtex, blitzbasic, bnf, boo, c, c_mac, caddcl, cadlisp, cfdg, cfm, cil, cmake, cobol, cpp, cpp-qt, csharp, css, d, dcs, delphi, diff, div, dos, dot, eiffel, email, erlang, fo, fortran, freebasic, genero, gettext, glsl, gml, gnuplot, groovy, haskell, hq9plus, html4strict, idl, ini, inno, intercal, io, java, java5, javascript, kixtart, klonec, klonecpp, latex, lisp, locobasic, lolcode, lotusformulas, lotusscript, lscript, lsl2, lua, m68k, make, matlab, mirc, modula3, mpasm, mxml, mysql, nsis, oberon2, objc, ocaml, ocaml-brief, oobas, oracle11, oracle8, pascal, per, perl, php, php-brief, pic16, pixelbender, plsql, povray, powershell, progress, prolog, properties, providex, python, qbasic, rails, rebol, reg, robots, ruby, sas, scala, scheme, scilab, sdlbasic, smalltalk, smarty, sql, tcl, teraterm, text, thinbasic, tsql, typoscript, vb, vbnet, verilog, vhdl, vim, visualfoxpro, visualprolog, whitespace, whois, winbatch, xml, xorg_conf, xpp, z80

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