Changes

== What is Sweets ==

== What is Sweets ==

So, Sweets is a [[wikipedia: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 the Sugar ecosystem, such as libraries, sugar itself, and sugar activities.

So, Sweets is a [[wikipedia:Package_management_system |Package Management System]] entirely based on [http://0install.net/ Zero Install], a decentralized, cross-distribution, software installation system. It might be treated as a tools and infrastructure wrapper around Zero Install. Sweets 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 assuming that:

The purpose is to create a new distribution method instead of reusing:

The purpose is to create a new distribution method instead of reusing:

# ''.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, 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}}.

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

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

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

# ''.xo bundles'' is a subset of the Sweets workflow

# [[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''