Platform Team/Package Management System/1.0/Notes: Difference between revisions

m moved Platform Team/Sweets/1.0/Notes to Platform Team/Package Management System/1.0/Notes: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"
 
(3 intermediate revisions by 2 users not shown)
Line 4: Line 4:


The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems that the core ideas have settled down and are ready to be presented widely in the community.
The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems that the core ideas have settled down and are ready to be presented widely in the community.
Announcement:
* [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg23055.html sugar-devel, 02 October 2011].
* [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/4627 zero-install-devel, 02 October 2011].


== The pillars ==
== The pillars ==
Line 41: Line 45:
At the same time, existing distribution methods are reused in Sweets:
At the same time, existing distribution methods are reused in Sweets:


# [[Development_Team/Almanac/Activity_Bundles|''.xo bundles'']] is a subset of the Sweets workflow from usage point of view
# [[Development_Team/Almanac/Activity_Bundles|''.xo bundles'']] is a subset of the Sweets workflow, from usage point of view
#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.
#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.
# ''native packages''
# ''native packages''