Changes

Jump to navigation Jump to search
Line 51: Line 51:  
* split implementations per language.
 
* split implementations per language.
   −
Zero Sugar natively supports ''forks'' (better name?) that are similar to [http://en.wikipedia.org/wiki/Fork_%28software_development%29 regular] forks in FOSS but could be 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.
    
Having urls as Zero packaging ids, it will be possible to:
 
Having urls as Zero packaging ids, it will be possible to:

Navigation menu