Platform Team/Package Management System/Architecture - Revision history

Alsroot: moved Platform Team/Sweets/Architecture to Platform Team/Package Management System/Architecture: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"

2012-04-27T10:11:18Z

moved Platform Team/Sweets/Architecture to Platform Team/Package Management System/Architecture: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"

← Older revision	Revision as of 06:11, 27 April 2012
(No difference)

Alsroot: /* Self-contained binary bundles */

2011-11-23T12:27:09Z

Self-contained binary bundles

← Older revision		Revision as of 08:27, 23 November 2011
Line 9:		Line 9:
	=== 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 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.		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:		To build a self-contained binary bundle, use the {{Code\|bindist}} command:

FGrose at 02:42, 23 November 2011

2011-11-23T02:42:13Z

← Older revision		Revision as of 22:42, 22 November 2011
Line 1:		Line 1:
	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 ==

FGrose at 02:41, 23 November 2011

2011-11-23T02:41:41Z

← Older revision		Revision as of 22:41, 22 November 2011
Line 9:		Line 9:
	=== 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~~, containing~~ all dependencies bundled. For binary based sweets, resulting bundle will contain binaries built only for the environment that is being used to create this bundle. Thus, make sure that bundle will be used in exactly the same environment as original one.		This mode is intended for special cases, when a sweet needs to be used without Zero Install and Sweets. In this mode all dependencies 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 self-contained binary bundle, use {{Code\|bindist}} command:		To build a self-contained binary bundle, use the {{Code\|bindist}} command:

	sweet bindist <SWEET>		sweet bindist <SWEET>

	The resulting bundle will be placed to the current directory.		The resulting bundle will be placed into the current directory.

	After extracting, it might be used in several ways:		After extracting, it might be used in several ways:

	* for libraries, source the shell file in {{Code\|<SWEET-NAME>/binding}} directory;		* 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}}.		* for applications, execute the script {{Code\|<SWEET-NAME>/<APPLICATION>}}, the default application name is {{Code\|run}}.

Alsroot: /* Self-contained binary bundles */

2011-11-22T23:02:04Z

Self-contained binary bundles

← Older revision		Revision as of 19:02, 22 November 2011
Line 19:		Line 19:
	After extracting, it might be used in several ways:		After extracting, it might be used in several ways:

	* for libraries, source the shell file in {{Code\|<~~SWEETS~~>/binding}} directory;		* for libraries, source the shell file in {{Code\|<SWEET-NAME>/binding}} directory;
	* for applications, execute the script {{Code\|<SWEET>/<~~application-name~~>}}, the default application name is {{Code\|run}}.		* for applications, execute the script {{Code\|<SWEET-NAME>/<APPLICATION>}}, the default application name is {{Code\|run}}.

	=== Sweet packages ===		=== Sweet packages ===

Alsroot: /* Self-contained binary bundles */

2011-11-22T23:01:08Z

Self-contained binary bundles

← Older revision		Revision as of 19:01, 22 November 2011
Line 14:		Line 14:

	sweet bindist <SWEET>		sweet bindist <SWEET>

			The resulting bundle will be placed to the current directory.

			After extracting, it might be used in several ways:

			* for libraries, source the shell file in {{Code\|<SWEETS>/binding}} directory;
			* for applications, execute the script {{Code\|<SWEET>/<application-name>}}, the default application name is {{Code\|run}}.

	=== Sweet packages ===		=== Sweet packages ===

Alsroot: /* Sweets delivery */

2011-11-22T22:56:26Z

Sweets delivery

← Older revision		Revision as of 18:56, 22 November 2011
Line 8:		Line 8:

	=== 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, containing all dependencies bundled. For binary based sweets, resulting bundle will contain binaries built only for the environment that is being used to create this bundle. Thus, make sure that bundle will be used in exactly the same environment as original one.

			To build self-contained binary bundle, use {{Code\|bindist}} command:

			sweet bindist <SWEET>

	=== Sweet packages ===		=== Sweet packages ===

Alsroot: /* Sweets distribution */

2011-11-07T12:55:37Z

Sweets distribution

← Older revision		Revision as of 08:55, 7 November 2011
Line 1:		Line 1:
	This guide covers basic Sweets concepts. See also [[Platform_Team/Sweets\|introduction page]].		This guide covers basic Sweets concepts. See also [[Platform_Team/Sweets\|introduction page]].

	== Sweets ~~distribution~~ ==		== Sweets delivery ==

	=== Zero Install ===		=== Zero Install ===

Alsroot: /* Sweets distribution */

2011-11-07T12:53:00Z

Sweets distribution

← Older revision		Revision as of 08:53, 7 November 2011
Line 5:		Line 5:
	=== Zero Install ===		=== Zero Install ===

	=== Sources ~~tarballs~~ ===		=== Sources bundles ===

	=== Self-contained binary ~~tarballs~~ ===		=== Self-contained binary bundles ===

	=== Sweet packages ===		=== Sweet packages ===

Alsroot: Created page with "This guide covers basic Sweets concepts. See also introduction page. == Sweets distribution == === Zero Install === === Sources tarballs === === Self..."

2011-11-07T12:52:23Z

Created page with "This guide covers basic Sweets concepts. See also introduction page. == Sweets distribution == === Zero Install === === Sources tarballs === === Self..."

New page

This guide covers basic Sweets concepts. See also [[Platform_Team/Sweets|introduction page]].

== Sweets distribution ==

=== Zero Install ===

=== Sources tarballs ===

=== Self-contained binary tarballs ===

=== Sweet packages ===

== Glossary ==

{{:Platform Team/Sweets/Glossary}}