5,705
edits
Changes
Talk:Platform Team/Package Management System (view source)
Revision as of 06:11, 27 April 2012
, 06:11, 27 April 2012moved Talk:Platform Team/Sweets to Talk:Platform Team/Package Management System: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"
=== Sugar developers ===
=== 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.
<strike>
Services are intended to decentralize Sugar development process. 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. For example:
* some features are of arguable general benefit; Sugar Services would allow interested end users to efficiently test (and even deploy) such features;
* some feature are only stable in limited environments; Sugar Services would allow deployment in limited environmets without the risk of destabilizing the rest of Sugar.
A developer benefits from 0install [http://0install.net/goals.html features] by:
A developer benefits from 0install [http://0install.net/goals.html features] by:
''Are not these following benefits for activity developers?''
''Are not these following benefits for activity developers?''
</strike> moved to "All sugar develpers" [[User:Alsroot|alsroot]] 14:25, 26 December 2009 (UTC)
<strike>
* providing libraries or applications that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]
* 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
** including libraries that are used by only a few activities; or
** have shorter or longer release/support schedules than Sucrose;
** 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.
* 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.
</strike> added to activity developers section [[User:Alsroot|alsroot]] 14:21, 26 December 2009 (UTC)
See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to learn how to create Sugar Services.
See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to learn how to create Sugar Services.
== Repositories support ==
There is no need in Services to have only http://download.sugarlabs.org/services/ repository, every developer could provide his own repo and activity developers should have a chance to use non download.sl.o services. [[User:Alsroot|alsroot]] 14:04, 17 January 2010 (UTC)