Sugar Labs

Platform Team/Package Management System

< Platform Team
Revision as of 04:13, 26 December 2009 by Alsroot (talk | contribs) (→‎All sugar developers)


Zero Sugar Distribution

Sugar Services provides transparency for users and convenience for activity developers across varying platforms (and their varying dependencies) as well as across Sugar releases. Sugar 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 techniques is that Sugar 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.

Workflows

Sugar Services looks different depending upon your point of view:

Users

In the case of a poor Internet connection (and implemented Zero Install integration feature), users can switch to offline mode and won't encounter any changes in their regular workflow. Switching to online mode brings additional progress bar to the launch dialog for activities that have pending/not-yet-downloaded/out-dated activity dependencies.

Activity developers

Sugar Services makes sense for activities that have non-Sugar Platform dependencies or support more then one Sucrose release cycle.

To utilize the benefits of Services, activity developer need only to mention all services that their activity is using. Services infrastructure will provide specified services (and specified versions) for the activity and will let activity know about them.

Use of non-Sugar Platform dependencies in activities

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. See Native packages usage to know how to utilize native packages in your activity or service.

All sugar developers

Services are intended to decentralize sugar development process e.g. if you have some idea in mind, you can start pushing it through entirely release queue to get it in the next(maybe not nearest) Sucrose release. The core issue here is that there are only YES and NO answers to inclusion your feature to Sucrose, so if there is 51% against and 49% for inclusion, feature could be rejected/postponed. Services make development process more flexible and let developer benefit 49% of users.

Any developer can get benefits from 0install features to:

  • let users of all(if service is not tied to particular sugar) deployed sugars, benefit from your feature instead of having it only in last Sucrose release;
    for example Activity Triggers services
  • provide libraries or applications that are not intended to be included to Sugar Platform
    • could be used by few activities
    • have shorter or longer release/support schedules
  • deploy dependencies that are specific to particular activity e.g. some python activities have C libraries, using Services, activity developer should not bundle all binaries that sugar supports but provide links to binaries that he managed to build and let Services build C libraries from sources on user side in the rest of cases

See Service Developers Guide to know how to create service.

Detailed description

This proposal assumes that the core of Sugar development (in common sense) is a wide variety of developers, not just those developers who are taking part in Sugar core (glucose) development. It is all about seeing Sugar activity development from an activity/3rd-party developer's point of view.

From such new core POV, sugar development process will look like:

  • variety of Sugar activities
  • that use variety of Sugar Services

So, developers use a set of services that have their own API changes based schedules. Glucose could be wrapped to regular service(s) with proper versioning scheme as well e.g. if glucose's activity API wasn't backwards compatibility broken since 0.82(glucose-0.x service) all activities that requires glucose 0 will be launched but instead of launching activities with requirements glucose 1, user will be warned about outdated sugar environment.

The corner stone of Sugar Services proposal is Saccharin library. This library provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be a part of glucose (some of its releases) or bundled to .xo otherwise.

FAQ

A short list of questions that describe Sugar Services' purposes.

What is Sugar Services not?

  • It is not intended to cure all ills.
  • It is not "must have" for activity developers; use it only if you really need it.
  • Is is not a replacement for GNU/Linux distributions Sugar packaging efforts; Sugar Services places no need for special treatment regarding dependencies as part of the Sugar Platform.
  • It is not intended to be used to support large packages (such as Qt or Firefox) in parallel with distributions. Sugar Services should not be used to avert scenarios such as "It is too bad that you don't have Firefox-3.5 in your three-year-old distribution and cannot run last Browse activity." In such cases, we should require that users update their distribution and Sugar Platform to more recent versions.

How is Sugar Services different?

  • From the point of view of 0install: Sugar Services is just a method to create 0install infrastructure; think about "apt" vs. "dpkg" or "yum" vs. "rpm". In other words, Sugar Services are an analog of 0release command localized to Sugar needs.
  • From the point of view of PackageKit: PackageKit provides a distribution-agnostic method to install already packaged software. Via 0install, Sugar Services let users install unpackaged software as well. More over, 0install will use PackageKit to install missed dependencies if they present in user's distribution.
  • From the point of view of GNU/Linux distributions: see the 0install original goals.

List of services

To see entirely list of services, go to http://download.sugarlabs.org/services/.

Documentation

TODO

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Platform_Team/Package_Management_System&oldid=42339"