Platform Team/Package Management System: Difference between revisions
| Line 69: | Line 69: | ||
* 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 | === How is Sugar Services different? === | ||
* '' | * ''From the point of view of [http://0install.net/ 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 [http://0install.net/0release.html 0release] command localized to Sugar needs. | ||
* '' | * ''From the point of view of [http://www.packagekit.org/ 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 [http://0install.net/goals.html original goals]. | ||
== List of services == | == List of services == | ||