Changes

** 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;

* 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.

* 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 these binaries, they could be used as regular activity dependencies.

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.