5,705
edits
Changes
Platform Team/Package Management System (view source)
Revision as of 10:23, 26 December 2009
, 10:23, 26 December 2009→Activity developers
* use dependencies that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]
* 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
** dependency is not part of Sugar Platform;
** including libraries that are used by only a few activities;
** 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 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.