5,705
edits
Changes
Platform Team/Package Management System (view source)
Revision as of 09:20, 26 December 2009
, 09:20, 26 December 2009→Activity developers
To utilize the benefits of Services, activity developer need only to [[Activity Team/Documentation/Services/Activity Developers Guide|mention]] all services that their activity is using. Services infrastructure will provide specified services (and specified versions) for the activity and [[Documentation_Team/Services/Activity_Developers_Guide#Attaching_dependencies_to_activity|will let activity know]] about them.
To utilize the benefits of Services, activity developer need only to [[Activity Team/Documentation/Services/Activity Developers Guide|mention]] all services that their activity is using. Services infrastructure will provide specified services (and specified versions) for the activity and [[Documentation_Team/Services/Activity_Developers_Guide#Attaching_dependencies_to_activity|will let activity know]] about them.
Sugar Services let activity developers:
* use dependencies 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;
* deploy 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 [[Documentation_Team/Services/Activity Developers Guide|Activity Developers Guide]] to know how to add service dependencies to your activity.
See [[Documentation_Team/Services/Activity Developers Guide|Activity Developers Guide]] to know how to add service dependencies to your activity.