Mer/Documentation/Getting your package included
(Cleanup, markup)
Line 1: Line 1:
-
== Getting your package included in the Repository ==
+
* 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>
-
* Make sure it compiles after getting your build dependancies, dpkg-buildpackage.
+
(This will add the source package to repository, and complain otherwise.)
-
* 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 <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.  
* 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
* Builder is at http://trac.tspre.org:8000
* Follow instructions, and submit job.
* Follow instructions, and submit job.
-
[[Category:Mer|Getting your package included]]
+
 
 +
 
 +
[[Category:Mer]]

Revision as of 09:29, 18 April 2009

  • 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

    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"