5,705
edits
Changes
Jump to navigation
Jump to search
Line 31:
Line 31: + + − + Line 40:
Line 42: + +
Platform Team/Sugar Packaging Management System (view source)
Revision as of 14:46, 26 April 2010
, 14:46, 26 April 2010→Implementation ideas
* Support several sucrose release that are popular in deployments right now, so activity developers won't have to code bunch of ifs to support several sucrose releases, they just use what current intermediate libraries can provide and activity will work (or gracefully fallback) on all sugars in the field.
* Support several sucrose release that are popular in deployments right now, so activity developers won't have to code bunch of ifs to support several sucrose releases, they just use what current intermediate libraries can provide and activity will work (or gracefully fallback) on all sugars in the field.
* Such libraries are designed to be 0install'ed instead of installing only from native packaging systems.
* Such libraries are designed to be 0install'ed instead of installing only from native packaging systems.
See [[Activity_Team/Polyol|Polyol group]] to know about possible implementation.
=== 0install deployment mechanism ===
=== 0install deployment mechanism ===
Intermediate level libraries will be especially useful if their recent versions could be installed on every sugar in the field in spite of the sucrose release on particular machine. 0install is obvious choice since it is (see [[Activity Team/Services|Sugar Services]] to know more about 0install support in sugar):
Intermediate level libraries will be especially useful if their recent versions could be installed on every sugar in the field in spite of the sucrose release on particular machine. 0install is obvious choice since it is:
* Over GNU/Linux distribution mechanism
* Over GNU/Linux distribution mechanism
Other, but not less, useful 0install feature is having several versions of the code in the same time. For example if activity can work only with particular version of some intermediate library, it will work with this exact version even if it is really old, of course this library version should be still supported.
Other, but not less, useful 0install feature is having several versions of the code in the same time. For example if activity can work only with particular version of some intermediate library, it will work with this exact version even if it is really old, of course this library version should be still supported.
See [[Activity Team/Services|Sugar Services]] to know about possible implementation.
== Activity developers point of view ==
== Activity developers point of view ==