5,705
edits
Changes
Platform Team/Package Management System (view source)
Revision as of 08:09, 27 September 2011
, 08:09, 27 September 2011→Summary
#* 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 [[Platform_Team/Sweets_Distribution|Sweets Distribution]], for example.
See also the initial release [[Platform_Team/Sweets/1.0/Notes|notes]].
== Zero Install basis ==
== Zero Install basis ==