10,505
edits
Changes
Jump to navigation
Jump to search
Talk:Platform Team/Package Management System (view source)
Revision as of 09:48, 26 December 2009
, 09:48, 26 December 2009Created page with '=== Sugar developers === Services are intended to decentralize Sugar development process. For example, if you have some idea in mind, you can start pushing it through the Sucros…'
=== Sugar developers ===
Services are intended to decentralize Sugar development process. For example, if you have some idea in mind, you can start pushing it through the Sucrose release queue to get it in the next (maybe not nearest) release. However, since the release process is binary—either your feature is included or not—Services offers more flexibility.
A developer benefits from 0install [http://0install.net/goals.html features] by:
* letting users of all deployed Sucrose releases benefit from your new feature instead of having it only in a specific (latest) Sucrose release; for example [[Documentation_Team/Services/Activity_Triggers|Activity Triggers]] services;
''Are not these following benefits for activity developers?''
* providing libraries or applications that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]
** including libraries that are used by only a few activities; or
** have shorter or longer release/support schedules than Sucrose;
* deploying dependencies that are specific to particular activity; for example, some Python activities include C libraries—by using Services, an activity developer need not bundle all the binaries that Sugar supports; links can be provided links to any binaries that have been build, Services will build additional C libraries from source on user side where they are required.
See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to learn how to create Sugar Services.
Services are intended to decentralize Sugar development process. For example, if you have some idea in mind, you can start pushing it through the Sucrose release queue to get it in the next (maybe not nearest) release. However, since the release process is binary—either your feature is included or not—Services offers more flexibility.
A developer benefits from 0install [http://0install.net/goals.html features] by:
* letting users of all deployed Sucrose releases benefit from your new feature instead of having it only in a specific (latest) Sucrose release; for example [[Documentation_Team/Services/Activity_Triggers|Activity Triggers]] services;
''Are not these following benefits for activity developers?''
* providing libraries or applications that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]
** including libraries that are used by only a few activities; or
** have shorter or longer release/support schedules than Sucrose;
* deploying dependencies that are specific to particular activity; for example, some Python activities include C libraries—by using Services, an activity developer need not bundle all the binaries that Sugar supports; links can be provided links to any binaries that have been build, Services will build additional C libraries from source on user side where they are required.
See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to learn how to create Sugar Services.