5,705
edits
Changes
Jump to navigation
Jump to search
Line 21:
Line 21: − For such activities, development focus is shifted from Sucrose to an API of services they are using. More over, an activity could be assigned to particular service API version (provided that service developers still support this branch); Sugar Services will support several branches for the same service simultaneously.+ − −
Platform Team/Package Management System (view source)
Revision as of 02:57, 26 December 2009
, 02:57, 26 December 2009→Activity developers
Sugar Services makes sense for activities that have non-Sugar Platform dependencies or support more then one Sucrose release cycle.
Sugar Services makes sense for activities that have non-Sugar Platform dependencies or support more then one Sucrose release cycle.
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 (or pure 0install feeds)]] that their activity is using. Services infrastructure will provide specified services (and specified versions) for the activity and will export environment variables, e.g., LD_LIBRARY_PATH or PYTHONPATH, to activity session. ''Activity developer need not to adapt their code to Services.''
=== Use of non-Sugar Platform dependencies in activities ===
=== Use of non-Sugar Platform dependencies in activities ===