5,705
edits
Changes
Jump to navigation
Jump to search
Line 49:
Line 49: − + +
Platform Team/Package Management System (view source)
Revision as of 02:52, 10 July 2010
, 02:52, 10 July 2010→Identification
* let user launch not only last version e.g. package can contain implementations for several branches or/and stabilities,
* let user launch not only last version e.g. package can contain implementations for several branches or/and stabilities,
* split binary implementations per OS and platform,
* split binary implementations per OS and platform,
* split implementations per language.
* split implementations per language,
* support forks.
Zero Sugar natively supports ''forks'' (better name?) that could be [http://en.wikipedia.org/wiki/Fork_%28software_development%29 regular forks] or just results of doers' experiments i.e. without intension to push changes to an upstream. Forks are regular Zero packages and identified by unique Web url but linked to an upstream package (by mentioning upstream url in [http://0install.net/interface-spec.html#id4015759 feed-for] metadata field). So, having an upstream activity http://go.sugarlabs.org/Record, http://A.doer.org/My_Record from doer A and http://B.doer.org/My_Record from doer B, user C will have Record implementations from three sources.
Zero Sugar natively supports ''forks'' (better name?) that could be [http://en.wikipedia.org/wiki/Fork_%28software_development%29 regular forks] or just results of doers' experiments i.e. without intension to push changes to an upstream. Forks are regular Zero packages and identified by unique Web url but linked to an upstream package (by mentioning upstream url in [http://0install.net/interface-spec.html#id4015759 feed-for] metadata field). So, having an upstream activity http://go.sugarlabs.org/Record, http://A.doer.org/My_Record from doer A and http://B.doer.org/My_Record from doer B, user C will have Record implementations from three sources.