Platform Team/Package Management System - Revision history

FGrose: link update

2012-07-03T19:51:05Z

link update

← Older revision		Revision as of 15:51, 3 July 2012
Line 26:		Line 26:
	#* Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software, i.e., dependencies, will be reused from native packages.		#* Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software, i.e., dependencies, will be reused from native packages.
	#* For cases like Sugar deployments, using the more centralized, regular repositories (third party or official GNU/Linux distributions with native packages) makes more sense. These native packages of Sugar software will be included in Sweets, as well. When people start using Sweets on top of these Sugar distributions, they will have the chance to choose between natively packaged Sugar components and components that came directly from software creators.		#* For cases like Sugar deployments, using the more centralized, regular repositories (third party or official GNU/Linux distributions with native packages) makes more sense. These native packages of Sugar software will be included in Sweets, as well. When people start using Sweets on top of these Sugar distributions, they will have the chance to choose between natively packaged Sugar components and components that came directly from software creators.
	#* It is possible, when there is a need, to automatically package sweets into native packages. See [[~~Community/Distributions/Sweets_Distribution\|~~Sweets Distribution]], for example.		#* It is possible, when there is a need, to automatically package sweets into native packages. See [[Sweets Distribution]], for example.

	See also the initial release [[Platform_Team/Sweets/1.0/Notes\|notes]].		See also the initial release [[Platform_Team/Sweets/1.0/Notes\|notes]].

Alsroot at 10:12, 27 April 2012

2012-04-27T10:12:47Z

@@ Line 1: / Line 1: @@
 == Summary ==
@@ Line 52: / Line 50: @@
 * [http://git.sugarlabs.org/sdk/sweets Sources].
 * Recipe files [[Platform_Team/Recipe_Specification|specification]].

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

2012-04-27T10:11:16Z

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

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

Alsroot: moved Platform Team/Sweets Distribution to Platform Team/Sweets over redirect

2012-03-01T08:10:20Z

moved Platform Team/Sweets Distribution to Platform Team/Sweets over redirect

← Older revision	Revision as of 04:10, 1 March 2012
(No difference)

Alsroot: moved Platform Team/Sweets to Platform Team/Sweets Distribution: "Sweets" itself is PMS, when "Sweets Distribution" is sucrose sweets repos

2012-03-01T08:09:19Z

moved Platform Team/Sweets to Platform Team/Sweets Distribution: "Sweets" itself is PMS, when "Sweets Distribution" is sucrose sweets repos

← Older revision	Revision as of 04:09, 1 March 2012
(No difference)

Alsroot: /* Summary */

2011-11-07T12:59:12Z

Summary

← Older revision		Revision as of 08:59, 7 November 2011
Line 28:		Line 28:
	#* Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software, i.e., dependencies, will be reused from native packages.		#* Sweets is not intended to create one more GNU/Linux distribution. It distributes only projects that people create within the Sugar community; all other software, i.e., dependencies, will be reused from native packages.
	#* For cases like Sugar deployments, using the more centralized, regular repositories (third party or official GNU/Linux distributions with native packages) makes more sense. These native packages of Sugar software will be included in Sweets, as well. When people start using Sweets on top of these Sugar distributions, they will have the chance to choose between natively packaged Sugar components and components that came directly from software creators.		#* For cases like Sugar deployments, using the more centralized, regular repositories (third party or official GNU/Linux distributions with native packages) makes more sense. These native packages of Sugar software will be included in Sweets, as well. When people start using Sweets on top of these Sugar distributions, they will have the chance to choose between natively packaged Sugar components and components that came directly from software creators.
	#* It is possible, when there is a need, to automatically package sweets into native packages. See [[~~Platform_Team~~/Sweets_Distribution\|Sweets Distribution]], for example.		#* It is possible, when there is a need, to automatically package sweets into native packages. See [[Community/Distributions/Sweets_Distribution\|Sweets Distribution]], for example.

	See also the initial release [[Platform_Team/Sweets/1.0/Notes\|notes]].		See also the initial release [[Platform_Team/Sweets/1.0/Notes\|notes]].

Alsroot at 12:46, 7 November 2011

2011-11-07T12:46:57Z

← Older revision		Revision as of 08:46, 7 November 2011
Line 35:		Line 35:

	Sweets is entirely based on Zero Install. Sweets might be treated as a tools and infrastructure wrapper around Zero Install. See Zero Install's home page, http://0install.net/, for detailed information. And the [http://0install.net/injector-design.html design] page in particular.		Sweets is entirely based on Zero Install. Sweets might be treated as a tools and infrastructure wrapper around Zero Install. See Zero Install's home page, http://0install.net/, for detailed information. And the [http://0install.net/injector-design.html design] page in particular.
	~~==Glossary==~~
	~~{{:Platform Team/Sweets/Glossary}}~~
	== Further reading ==		== Further reading ==

			* [[Platform_Team/Sweets/Architecture\|Sweets Architecture]] - A guide to basic Sweets concepts.
	* [[Platform_Team/Guide/Sweets_Usage\|Sweets Usage]] - A guide to know how to launch software using Sweets.		* [[Platform_Team/Guide/Sweets_Usage\|Sweets Usage]] - A guide to know how to launch software using Sweets.
	* [[Platform_Team/Guide/Sweets_Packaging\|Sweets Packaging]] - A guide to know how to make your software accessible via Sweets.		* [[Platform_Team/Guide/Sweets_Packaging\|Sweets Packaging]] - A guide to know how to make your software accessible via Sweets.

FGrose at 21:37, 2 October 2011

2011-10-02T21:37:09Z

← Older revision		Revision as of 17:37, 2 October 2011
Line 11:		Line 11:
	* 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 goal is to create a new distribution method, that goes beyond reusing the current methods:		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'']]

FGrose at 21:35, 2 October 2011

2011-10-02T21:35:16Z

Alsroot: /* Summary */

2011-10-02T16:36:08Z

Summary

← Older revision		Revision as of 12:36, 2 October 2011
Line 3:		Line 3:
	== Summary ==		== Summary ==

	Sweets is a [http://en.wikipedia.org/wiki/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.		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 assuming that:
Line 13:		Line 13:
	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}}.
Line 23:		Line 23:
	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''

← Older revision		Revision as of 17:35, 2 October 2011
Line 5:		Line 5:
	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''