Changes

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

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

# [[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, 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:

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