Difference between revisions of "Platform Team/Package Management System"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* The method to share software projects should to be as convenient as possible. | * The method to share software projects should to be as convenient as possible. | ||
* It is important to stimulate users into becoming doers, to modify existing activities, and to share the results of their experiments with other people, i.e., a distribution method should handle different variants of the same project. | * It is important to stimulate users into becoming doers, to modify existing activities, and to share the results of their experiments with other people, i.e., a distribution method should handle different variants of the same project. | ||
| − | * This distribution method is not intended to be the only one | + | * This distribution method is not intended to be the only one, but is targeted more towards direct distribution—from software creators to software users. |
The purpose is to create a new distribution method instead of reusing: | The purpose is to create a new distribution method instead of reusing: | ||
| Line 13: | Line 13: | ||
# ''.xo bundles'' | # ''.xo bundles'' | ||
#* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries. | #* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries. | ||
| − | #* | + | #* But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in {{Code|~/Activities}}. |
# ''native packages'' | # ''native packages'' | ||
| − | #* Not the shortest way | + | #* Not the shortest way to connect developers with users. |
#* In most cases, they don't support multiple versions of the same project. | #* In most cases, they don't support multiple versions of the same project. | ||
#* They don't work at all for sharing results of experiments. | #* They don't work at all for sharing results of experiments. | ||
| Line 25: | Line 25: | ||
# ''native packages'' | # ''native packages'' | ||
#* Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software, i.e., dependencies, will be reused from native packages. | #* Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software, i.e., dependencies, will be reused from native packages. | ||
| − | #* | + | #* For cases like Sugar deployments, using the more centralized, regular repositories (third party or official GNU/Linux distributions with native packages) makes more sense. These native packages of Sugar software will be included in Sweets, as well. When people start using Sweets on top of these Sugar distributions, they will have the chance to choose between natively packaged Sugar components and components that came directly from software creators. |
| − | #* It is possible, when there is a need, to automatically package sweets into native packages. See [[Platform_Team/Sweets_Distribution|Sweets Distribution]] for example. | + | #* It is possible, when there is a need, to automatically package sweets into native packages. See [[Platform_Team/Sweets_Distribution|Sweets Distribution]], for example. |
== Zero Install basis == | == Zero Install basis == | ||
| − | Sweets is entirely based on Zero Install. | + | Sweets is entirely based on Zero Install. Sweets might be treated as a tools and infrastructure wrapper around Zero Install. See Zero Install's home page, http://0install.net/, for detailed information. |
== Dictionary == | == Dictionary == | ||
| Line 36: | Line 36: | ||
| − | == | + | == Further reading == |
| − | * | + | * [[Platform_Team/Guide/Sweets_Usage|Sweets Usage]] - A guide to know how to launch software using Sweets. |
| − | * | + | * [[Platform_Team/Guide/Sweets_Packaging|Sweets Packaging]] - A guide to know how to make your software accessible via Sweets. |
| − | * | + | * [[Platform_Team/Infrastructure|Infrastructure Map]] - An overview of the Sweets software world. |
== Getting involved == | == Getting involved == | ||
Revision as of 08:15, 4 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 the Sugar ecosystem, such as libraries, sugar itself, and sugar activities.
This 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 into becoming doers, to modify existing activities, and to share the results of their experiments with other people, i.e., a distribution method should handle different variants of the same project.
- This distribution method is not intended to be the only one, but is targeted more towards direct distribution—from software creators to software users.
The purpose is to create a new distribution method instead of reusing:
- .xo bundles
- Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.
- But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in
~/Activities.
- native packages
- Not the shortest way to connect developers with users.
- In most cases, they don't support multiple versions of the same project.
- They don't work at all for sharing results of experiments.
At the same time, existing distribution methods are reused in Sweets:
- .xo bundles is a subset of the Sweets workflow
- It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.
- native packages
- Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software, i.e., dependencies, will be reused from native packages.
- For cases like Sugar deployments, using the more centralized, regular repositories (third party or official GNU/Linux distributions with native packages) makes more sense. These native packages of Sugar software will be included in Sweets, as well. When people start using Sweets on top of these Sugar distributions, they will have the chance to choose between natively packaged Sugar components and components that came directly from software creators.
- It is possible, when there is a need, to automatically package sweets into native packages. See Sweets Distribution, for example.
Zero Install basis
Sweets is entirely based on Zero Install. Sweets might be treated as a tools and infrastructure wrapper around Zero Install. See Zero Install's home page, http://0install.net/, for detailed information.
Dictionary
Further reading
- Sweets Usage - A guide to know how to launch software using Sweets.
- Sweets Packaging - A guide to know how to make your software accessible via Sweets.
- Infrastructure Map - An overview of the Sweets software world.
Getting involved
Resources
- Sources.
- Recipe files specification.