Changes

Sweets is a [http://en.wikipedia.org/wiki/Package_management_system Package Management System] entirely based on [http://0install.net/ 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.

Sweets is a [http://en.wikipedia.org/wiki/Package_management_system Package Management System] entirely based on [http://0install.net/ 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:

This new distribution method is initiated with these assumptions:

* 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, viz., 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.

* 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 goal is to create a new distribution method, that goes beyond reusing the current methods:

# [[Development_Team/Almanac/Activity_Bundles|''.xo bundles'']]

# [[Development_Team/Almanac/Activity_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, though 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}}.

#* But, are not effective in supporting the simultaneous use of multiple versions of software, e.g., the results of experiments (the work) of different doers, in one environment. 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 to connect developers with users.

#* Are 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.

At the same time, existing distribution methods are reused in Sweets:

And, at the same time, the existing distribution methods are available for reuse 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'']] are a subset of the Sweets workflow, from the 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''