Mer/Build/Processes
(add feedback echo) |
(→To Promote :Testing to :Stable) |
||
| Line 101: | Line 101: | ||
for i in $(osc ls Maemo:Mer:Stable:$HW); do echo $i; osc rdelete Maemo:Mer:Stable:$HW $i; done | for i in $(osc ls Maemo:Mer:Stable:$HW); do echo $i; osc rdelete Maemo:Mer:Stable:$HW $i; done | ||
done | done | ||
| + | |||
| + | *** ALSO wipebinaries next time *** | ||
NOTE The following uses -m in osc which is not accepted upstream yet. It will not work unless you have lbt's osc patches. | NOTE The following uses -m in osc which is not accepted upstream yet. It will not work unless you have lbt's osc patches. | ||
Revision as of 09:55, 20 July 2009
OBS Project structure and promotion
The Mer projects on OBS look like this:
Maemo:Mer:Stable Maemo:Mer:Stable:HW:Beagle Maemo:Mer:Stable:HW:N8x0
This means all devices will have the main 'Stable' repository and an appropriate HW repository.
The development area is expanded slightly:
Maemo:Mer:Devel:Apps Maemo:Mer:Devel:Base Maemo:Mer:Devel:MaemoCommon Maemo:Mer:Devel:MaemoCommon:L10n Maemo:Mer:Devel:UI Maemo:Mer:Devel:HW:Beagle:Devel Maemo:Mer:Devel:HW:N8x0:Devel
Details of packages in each area is given in thePackages pages.
Packages in each of these Devel subproject areas can be hacked on and then, when they're kinda working they are consolidated into the :Devel area (which is used as a build target for the :Devel:* subprojects)
Maemo:Mer:Devel Maemo:Mer:Devel:HW:N8x0 Maemo:Mer:Devel:HW:Beagle
Packages are placed in :Testing with the intention of including them in the next release subject to QA and bug fixes
Maemo:Mer:Testing Maemo:Mer:Testing:HW:Beagle Maemo:Mer:Testing:HW:N8x0
Once :Testing is ready a release of all packages to a numbered version is made:
Maemo:Mer:0.13 Maemo:Mer:0.13:HW:Beagle Maemo:Mer:0.13:HW:N8x0
Note that the :HW promotion process is slightly different:
Maemo:Mer:Devel:HW:N8x0:Devel -> Maemo:Mer:Devel:HW:N8x0 -> Maemo:Mer:Testing:HW:N8x0 -> Maemo:Mer:Stable:HW:N8x0
Promotion Tasks
To promote a package:
osc copypac <SOURCEPRJ> <SOURCEPAC> <DESTPRJ>
eg:
osc copypac -k Maemo:Mer:Devel glib2.02 Maemo:Mer:Testing
The -k ensures that the maintainer info is preserved.
Ensure that:
osc meta prjconfInvalid 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