Changes

Jump to navigation Jump to search
m
link update
Line 1: Line 1: −
{{Template:Sweets Cycle Linkbar}}
  −
   
== Summary ==
 
== Summary ==
   Line 28: 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 [[Platform_Team/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]].
Line 35: Line 33:     
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.
Line 52: Line 50:  
* [http://git.sugarlabs.org/sdk/sweets Sources].
 
* [http://git.sugarlabs.org/sdk/sweets Sources].
 
* Recipe files [[Platform_Team/Recipe_Specification|specification]].
 
* Recipe files [[Platform_Team/Recipe_Specification|specification]].
 +
 +
== Subpages ==
 +
 +
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Navigation menu