5,705
edits
Changes
Jump to navigation
Jump to search
Line 43:
Line 43: − − == What Sugar Services are not == − − * It is ''not'' intended to cure all ills. − * It is ''not'' "must have" for activity developers; use it only if you really [[#Work_flows|need]] it. − * Is is ''not'' a replacement for GNU/Linux distributions Sugar packaging efforts; Sugar Services places no need for special treatment regarding dependencies as part of the [[0.86/Platform_Components|Sugar Platform]]. − * It is ''not'' intended to be used to support large packages (such as Qt or Firefox) in parallel with distributions. Sugar Services should ''not'' be used to avert scenarios such as ''"It is too bad that you don't have Firefox-3.5 in your three-year-old distribution and cannot run last Browse activity."'' In such cases, we should require that users update their distribution and Sugar Platform to more recent versions. Line 64:
Line 57: + + + + + + + + + + + + +
Platform Team/Package Management System (view source)
Revision as of 05:16, 24 December 2009
, 05:16, 24 December 2009no edit summary
The entirety of the Sugar Services feature is nothing but a Sugarized UI built around [http://0install.net/ 0install]; i.e., feed files that are being used in activity bundles are just regular 0install local feeds. Services could be used to install/upgrade any software (including sugar core components).
The entirety of the Sugar Services feature is nothing but a Sugarized UI built around [http://0install.net/ 0install]; i.e., feed files that are being used in activity bundles are just regular 0install local feeds. Services could be used to install/upgrade any software (including sugar core components).
== Detailed description ==
== Detailed description ==
Technically, Sugar Services could be a part of glucose (or some of its releases) but from activity POV it doesn't make much sense. If an activity requires some service, [[Activity_Team/Services/Saccharin|Saccharin]] will do nothing if requested service/version is already a part of the installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.
Technically, Sugar Services could be a part of glucose (or some of its releases) but from activity POV it doesn't make much sense. If an activity requires some service, [[Activity_Team/Services/Saccharin|Saccharin]] will do nothing if requested service/version is already a part of the installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.
== FAQ ==
Short list of questions that describe Sugar Services.
=== What Sugar Services are not ===
* It is ''not'' intended to cure all ills.
* It is ''not'' "must have" for activity developers; use it only if you really [[#Work_flows|need]] it.
* Is is ''not'' a replacement for GNU/Linux distributions Sugar packaging efforts; Sugar Services places no need for special treatment regarding dependencies as part of the [[0.86/Platform_Components|Sugar Platform]].
* It is ''not'' intended to be used to support large packages (such as Qt or Firefox) in parallel with distributions. Sugar Services should ''not'' be used to avert scenarios such as ''"It is too bad that you don't have Firefox-3.5 in your three-year-old distribution and cannot run last Browse activity."'' In such cases, we should require that users update their distribution and Sugar Platform to more recent versions.
=== What Sugar Services are not ===
== List of services ==
== List of services ==