5,705
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − + Line 8:
Line 8: + + + + + + + + + + + + +
Platform Team/Package Management System/Architecture (view source)
Revision as of 06:11, 27 April 2012
, 06:11, 27 April 2012moved Platform Team/Sweets/Architecture to Platform Team/Package Management System/Architecture: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"
This guide covers basic Sweets concepts. See also [[Platform_Team/Sweets|introduction page]].
This guide covers basic Sweets concepts. See also the [[Platform_Team/Sweets|introduction page]].
== Sweets delivery ==
== Sweets delivery ==
=== Self-contained binary bundles ===
=== Self-contained binary bundles ===
This mode is intended for special cases, when a sweet needs to be used without Zero Install and Sweets. In this mode all dependencies that are accessible via Sweets, i.e., not those that come from native packages, are bundled. For binary based sweets, the resulting bundle will contain binaries built only for the environment that is being used to create this bundle. Thus, make sure that the new bundle will be used in exactly the same environment as the original one.
To build a self-contained binary bundle, use the {{Code|bindist}} command:
sweet bindist <SWEET>
The resulting bundle will be placed into the current directory.
After extracting, it might be used in several ways:
* for libraries, source the shell file in the {{Code|<SWEET-NAME>/binding}} directory;
* for applications, execute the script {{Code|<SWEET-NAME>/<APPLICATION>}}, the default application name is {{Code|run}}.
=== Sweet packages ===
=== Sweet packages ===