5,705
edits
Changes
Jump to navigation
Jump to search
Line 57:
Line 57: − +
Platform Team/Package Management System (view source)
Revision as of 10:06, 26 December 2009
, 10:06, 26 December 2009→Detailed description: do not mess packaged glucose with regular services
* variety of Sugar activities
* variety of Sugar activities
* that use variety of Sugar Services
* that use variety of Sugar Services
So, developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API changes based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to regular service(s) with proper [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|versioning scheme]] as well e.g. if glucose's activity API wasn't backwards compatibility broken since 0.82(glucose-0.x service) all activities that requires ''glucose 0'' will be launched but instead of launching activities with requirements ''glucose 1'', user will be warned about outdated sugar environment.
So, developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API changes based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to regular service(s) as well, which let developers target their activity or services for particular glucose versions and warn users about outdated sugar environment.
The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be a part of glucose (some of its releases) or bundled to .xo otherwise.
The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be a part of glucose (some of its releases) or bundled to .xo otherwise.