5,705
edits
Changes
Jump to navigation
Jump to search
Line 69:
Line 69: − + + + + + + +
Platform Team/Package Management System (view source)
Revision as of 04:31, 24 December 2009
, 04:31, 24 December 2009→How Sugar Services are different to
* 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.
* 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 Sugar Services are different to ===
=== How Sugar Services are different ===
* ''to [http://0install.net/ 0install]'', Service is just a method to create 0install infrastructure e.g. think about apt vs. dpkg or yum vs. rpm, in other words Services is an analog of [http://0install.net/0release.html 0release] command
* ''to [http://www.packagekit.org/ PackageKit]'', PackageKit provides distribution agnostic method to install already packaged software. Via 0install, Services let users install not (well)packaged software as well. More over, 0install will use PackageKit to install missed dependencies if they present in user's distribution
* ''to various GNU/Linux distributions'', see 0install [http://0install.net/goals.html original goals]
== List of services ==
== List of services ==