Difference between revisions of "Platform Team/Package Management System"

From Sugar Labs
Jump to navigation Jump to search
m (moved Platform Team/Sugar Doers Kit to Platform Team/Sweets: It seems that SDK's purpose is exactly the Platform Team's one, better to be concentrated only on Sweets.)
Line 1: Line 1:
−
{{Template:SDK Cycle Linkbar}}
+
== Summary ==
  
−
== The purpose ==
+
Sweets is a [http://en.wikipedia.org/wiki/Package_management_system Package Management System] based on [http://0install.net/ Zero Install], a decentralized cross-distribution software installation system. It is intended to distribute various software projects created in Sugar ecosystem such as libraries, sugar itself, sugar activities.
  
−
{{:{{PAGENAME}}/Purpose}}
+
New distribution method is initiated assuming that:
 +
 
 +
* The method to share software projects should to be as convenient as possible.
 +
* It is important to stimulate users being doers, change existed activities and share results of experiments between other people, i.e., distribution method should handle different variants of the same project.
 +
* This distribution method is not intended to be the only one.
 +
 
 +
The purpose to create new distribution method instead of reusing:
 +
 
 +
* ''.xo bundles''
 +
** Work smooth only for pure python activities and only if all (and the same) dependencies are installed on all systems. It stop working smooth if activities use non-standard dependencies or contain binaries.
 +
** Users need to manually handle the variety of activity versions, e.g., sort out all local bundles or directories in {{Code|~/Activities}}.
 +
* ''native packages''
 +
** Not the shortest way between developers and users.
 +
** In most cases it doesn't support multiple versions of the same project.
 +
** It doesn't work at all for sharing results of experiments.
 +
 
 +
At the same time existed distribution methods are reused in Sweets:
 +
 
 +
* ''.xo bundles'' is a subset of Sweets workflow
 +
** It is possible to bundle entirely directory with sweet project to use it as a regular .xo file.
 +
* ''native packages''
 +
** Sweets is not an intention to create one more GNU/Linux distribution. It distributes only projects people create within Sugar community, the rest of software will be reused from native packages.
  
 
== Start from ==
 
== Start from ==
  
−
Start from these pages if you are:
+
Start from these pages:
  
−
* [[Platform Team/Sugar Doers Kit/Overview|SDK overview]]
+
* [[Platform_Team/Guide/Sweets_Usage|Sweets Usage]] guide.
−
* [[Platform_Team/Guide/Core_development|Core developer or need to start core projects from sources]],
 
−
* [[Platform_Team/Guide/Activity_development|Activity developer]],
 
−
* [[Platform_Team/Overview|Want to know how Platform Team functions]].
 

Revision as of 21:44, 3 September 2011

Summary

Sweets is a Package Management System based on Zero Install, a decentralized cross-distribution software installation system. It is intended to distribute various software projects created in Sugar ecosystem such as libraries, sugar itself, sugar activities.

New distribution method is initiated assuming that:

  • The method to share software projects should to be as convenient as possible.
  • It is important to stimulate users being doers, change existed activities and share results of experiments between other people, i.e., distribution method should handle different variants of the same project.
  • This distribution method is not intended to be the only one.

The purpose to create new distribution method instead of reusing:

  • .xo bundles
    • Work smooth only for pure python activities and only if all (and the same) dependencies are installed on all systems. It stop working smooth if activities use non-standard dependencies or contain binaries.
    • Users need to manually handle the variety of activity versions, e.g., sort out all local bundles or directories in ~/Activities.
  • native packages
    • Not the shortest way between developers and users.
    • In most cases it doesn't support multiple versions of the same project.
    • It doesn't work at all for sharing results of experiments.

At the same time existed distribution methods are reused in Sweets:

  • .xo bundles is a subset of Sweets workflow
    • It is possible to bundle entirely directory with sweet project to use it as a regular .xo file.
  • native packages
    • Sweets is not an intention to create one more GNU/Linux distribution. It distributes only projects people create within Sugar community, the rest of software will be reused from native packages.

Start from

Start from these pages:

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Platform_Team/Package_Management_System&oldid=69009"