Difference between revisions of "Platform Team/Package Management System"

From Sugar Labs
Jump to navigation Jump to search
m (link update)
 
(85 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
<noinclude>
+
== Summary ==
−
  {{TOCright}}
 
−
  [[Category:Activity Team]]
 
−
</noinclude>
 
  
−
== Zero Sugar Distribution ==
+
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.
  
−
Zero Sugar provides a method that is transparent for users and convenient for doers to deploy software across varying platforms as well as across Sugar releases. Zero Sugar is mainly targeting to support direct doer-to-user interaction model i.e. without transmissive chain of doer-to-distributor-to-user (but Zero Sugar could be still [[#Distributors|useful]] for distributors since it unifies deployment workflow).
+
This new distribution method is initiated with these assumptions:
  
−
== Benefits ==
+
* The method to share software projects should to be as convenient as possible.
 +
* It is important to stimulate users into becoming doers&mdash;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&mdash;from software creators to software users.
  
−
How Zero Sugar could be useful depending upon your point of view:
+
The goal is to create a new distribution method that goes beyond reusing the current methods:
  
−
=== Users ===
+
# [[Development_Team/Almanac/Activity_Bundles|''.xo bundles'']]
 +
#* 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 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''
 +
#* Are not the shortest way to connect developers with users.
 +
#* In most cases, they don't support multiple versions of the same project.
 +
#* They don't work at all for sharing results of experiments.
  
−
Users can run sugar in various environments (machine architectures, GNU/Linux distributions etc.) and since sugar also stimulates users to be doers, there could be tons of handmade software in the field (mostly duplicates and reinvented wheels but it is nature of sugar i.e. process does matter). It is becoming critical to provide easy and robust launching scheme for all these pieces of code without writing long HOWTOs somewhere on wiki like "Please, if you are on Ubuntu, install these packages before starting my activity...".
+
And, at the same time, the existing distribution methods are available for reuse in Sweets:
  
−
Relying only on particular distributor i.e. using activities only from distributor's channel makes sugar not so useful. Zero Sugar provides direct deployment method between author of code and its users in as convenient as possible way.
+
# [[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.
 +
# ''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.
 +
#* It is possible, when there is a need, to automatically package sweets into native packages. See [[Sweets Distribution]], for example.
  
−
=== Doers ===
+
See also the initial release [[Platform_Team/Sweets/1.0/Notes|notes]].
  
−
Author of code all time is interested in supporting as big as possible users audience. And since people can use sugar in different environments, it is critical to provide instrument which allows to run activity on all sugar platforms. In case of python (only python, not even arbitrary scripting language since python is a part of [[0.88/Platform_Components|Sugar Platform]]) based activities, existed practice with just zipping activity to .xo files works pretty well. But it is a problem with non-python activities or activities that have dependencies not included to Sugar Platform.
+
== Zero Install basis ==
  
−
Zero Sugar tries to solve possible issues that prevent activity launching in heterogeneous Sugar environment.
+
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.
  
−
Also, if you have some idea in mind, you can start pushing it through the Sucrose release queue to get it into an upcoming (maybe not the nearest) release. However, since the release process is binary—either your feature is included or not—Zero Sugar offers more flexibility. For example:
+
== Further reading ==
−
* some features are of arguable general benefit; Zero Sugar would allow interested end users to efficiently test (and even deploy) such features;
 
−
* some feature are only stable in limited environments; Zero Sugar would allow deployment in limited environments without the risk of destabilizing the rest of Sugar.
 
  
−
=== Distributors ===
+
* [[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_Packaging|Sweets Packaging]] - A guide to know how to make your software accessible via Sweets.
 +
* [[Platform_Team/Infrastructure|Infrastructure Map]] - An overview of the Sweets software world.
  
−
The [[0.86/Platform_Components|Sugar Platform]] cannot grow endlessly, e.g., installing sugar from packages should not fetch half of all available packages including several UI toolkits, several programming languages, etc., so components like Qt or Ruby are (at least at present) out of the Sugar Platform list. But with Zero Sugar, activities can still use such dependencies by installing them from native packaging systems on demand and without bundling binaries.
+
== Getting involved ==
  
−
== How it works at glance ==
+
* Read the [http://git.sugarlabs.org/sdk/sweets/blobs/master/HACKING HACKING] file to know how to contribute with code.
 +
{{:Platform_Team/Sweets/Feedback}}
  
−
Instruments and services that are used within Zero Sugar:
+
== Resources ==
−
* [[Activity Team/Zero Sugar/0sugar|0sugar]] main tool, everything happen via ''0sugar'' command
 
−
* [http://0install.net/ 0install] decentralized deployment infrastructure
 
−
* [http://build.opensuse.org/ OBS] openSUSE Build Service, build farms and repository of native packages for GNU/Linux distributions OBS supports
 
−
* [http://www.packagekit.org/ PackageKit] to install software from native packaging systems
 
−
* [http://download.sugarlabs.org/ Sugar Labs]'s resources to host various files
 
  
−
Departing point is a [[Activity Team/Zero Sugar/Service.info Specification|spec file]] which is used by ''0sugar'' command to accomplish two major tasks:
+
* [http://git.sugarlabs.org/sdk/sweets Sources].
−
* how to build application and its dependencies
+
* Recipe files [[Platform_Team/Recipe_Specification|specification]].
−
* how to deploy application and its dependencies
 
  
−
Building might happen:
+
== Subpages ==
−
* building is not required for scripting languages
 
−
* on developer's box, to deploy to environments similar to developer's
 
−
* on OBS, to build on GNU/Linux distributions OBS supports
 
  
−
Deploying will happen:
+
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
−
* via 0install infrastructure to install:
 
−
** software that were built by developer, downloading from http://download.sugarlabs.org/
 
−
** packages will be downloaded from OBS repositories if build happened on OBS
 
−
** 0install might install application and its dependencies from native packages if PackageKit is installed
 
−
* via native packages, only if build happened on OBS; users need to follow regular, for their distributions, workflow to attach external OBS repository
 
−
 
 
−
== Documentation ==
 
−
 
 
−
Start your exploration from:
 
−
 
 
−
* [[Documentation Team/Services/Activity Developers Guide|Activity Developers Guide]] to get instructions how to use the already created Zero Sugar packages in activities
 
−
* [[Documentation Team/Services/Service Developers Guide|Service Developers Guide]] for how to create Zero Sugar package
 
−
 
 
−
See [[Activity Team/Zero Sugar/Scalable development model|Scalable development model]] to learn more about the initial intentions for Zero Sugar.
 

Latest revision as of 14:51, 3 July 2012

Summary

Sweets is a Package Management System entirely based on 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 with these assumptions:

  • 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, 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.

The goal is to create a new distribution method that goes beyond reusing the current methods:

  1. .xo bundles
    • 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 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 ~/Activities.
  2. native packages
    • Are not the shortest way to connect developers with users.
    • In most cases, they don't support multiple versions of the same project.
    • They don't work at all for sharing results of experiments.

And, at the same time, the existing distribution methods are available for reuse in Sweets:

  1. .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.
  2. 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.
    • 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 notes.

Zero Install basis

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 design page in particular.

Further reading

Getting involved

  • Read the HACKING file to know how to contribute with code.
  • Submit your bug report or feature request.
  • Subscribe to the sugar-devel mailing list and email with the subject prefixed with [SWEETS].
  • Ask your question on IRC channels, #sugar (not logged) or #sugar-newbies (logged).

Resources

Subpages

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Platform_Team/Package_Management_System&oldid=80472"