10,579
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − Provides transparent for users and convenient for activity developers, method to support variety of activity dependencies and variety of dependency versions. In other words Services is a common deployment system for activity dependencies, lightweight like sugargame and hightweight like Qt.+ − +
Platform Team/Package Management System (view source)
Revision as of 08:54, 20 December 2009
, 08:54, 20 December 2009→Summary
== Summary ==
== Summary ==
Services provides transparency for users and convenience for activity developers across varying platforms (and their varying dependencies) as well as across Sugar releases. Services is a method to support this variety of activity dependencies and variety of dependency versions. In other words, Services is a common deployment system for activity dependencies; it is lightweight like sugargame and like Qt.
The major difference from existed sugar deployment technics is that Services is activity developers POV system. It doesn't exclude(because reuse them) Sucrose releases or GNU/Linux distribution initiatives but gives activity developers additional(and optional) instrument.
The major difference from existed sugar deployment techniques is that Services has a point of view of the activity developer. It doesn't exclude (because it reuses them) Sucrose releases or GNU/Linux distribution initiatives, but it does give activity developers an additional (optional) instrument.
== Work flows ==
== Work flows ==