Platform Team/Package Management System: Difference between revisions
No edit summary |
|||
| Line 5: | Line 5: | ||
== 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 | 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 == | ||