8,288
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − {{TOCright}} Line 19:
Line 18: − + Line 27:
Line 26: − + − +
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 10:51, 17 September 2010
, 10:51, 17 September 2010no edit summary
[[Category:Zero Sugar]]
[[Category:Zero Sugar]]
<0install-feed-url>
<0install-feed-url>
At the end, all links will be transfered to 0install feed urls. The final 0install url will be in format:
At the end, all links will be transfered to 0install feed urls. The final 0install url will be in the following format:
<nowiki>http</nowiki>://sweets.sugarlabs.org/<Bazaar-project>/<slug>
<nowiki>http</nowiki>://sweets.sugarlabs.org/<Bazaar-project>/<slug>
The versioning scheme for Zero packages can be arbitrary, since the ''version'' recipe option supports [http://0install.net/interface-spec.html#id4016582 0install version format]. But in some cases, e.g., libraries, stricter versioning could be useful. In that case, the ''age'' recipe option should be used.
The versioning scheme for Zero packages can be arbitrary, since the ''version'' recipe option supports [http://0install.net/interface-spec.html#id4016582 0install version format]. But in some cases, e.g., libraries, stricter versioning could be useful. In that case, the ''age'' recipe option should be used.
The recipe option ''age'' is intended to support, mostly, API breakages of library packages. But not ABI, because tracking an ABI is not trivial within the Sugar ecosystem (due to the enormous potential code base of varying quality) and of little utility, since packages may at any time rebuild from sources and multiple library versions may be installed (thanks to 0install).
The recipe option ''age'' is intended to support, mostly, API breakages of library packages. But not ABI, because tracking an ABI is not trivial within the Sugar ecosystem (due to the enormous potential code base of varying quality) and of little utility, and since packages may at any time be rebuilt from sources and multiple library versions may be installed (thanks to 0install).
Using the ''age'' option is simple, on every API breakage for the library package, increment the ''age'' value. Final package version will be:
Using the ''age'' option is simple, on every API breakage for the library package, increment the ''age'' value. The final package version will be:
<age-option>.<version-option>
<age-option>.<version-option>