5,705
edits
Changes
Jump to navigation
Jump to search
Line 23:
Line 23: − + − +
Platform Team/Package Management System (view source)
Revision as of 05:40, 26 December 2009
, 05:40, 26 December 2009→Use of non-Sugar Platform dependencies in activities
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.
=== Use of non-Sugar Platform dependencies in activities ===
=== Distributors ===
The Sugar Platform cannot grow endlessly and components like Qt or OO4Kids are (at least at present) out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems without bundling binaries.
The [[0.86/Platform_Components|Sugar Platform] cannot grow endlessly e.g. installing sugar from packages should not fetch a half of all available packages including several UI toolkits, several programming languages etc., so components like Qt or OO4Kids are (at least at present) out of Sugar Platform list. But with Sugar Services, activities can still use such dependencies by installing them from native packaging systems by demand and without bundling binaries.
See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.
See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.