Difference between revisions of "Documentation Team/Obsolete/Services Wrap native packages HOWTO"
| Line 11: | Line 11: | ||
To use native packages, they should be wrapped into services. Such services are lightweight and contain only proper information about native packages. Also having service wrappers let us collect all distro specific information in one place, because various GNU/Linux distributions could have different names for the same upstream application. | To use native packages, they should be wrapped into services. Such services are lightweight and contain only proper information about native packages. Also having service wrappers let us collect all distro specific information in one place, because various GNU/Linux distributions could have different names for the same upstream application. | ||
| − | + | In according to http://distrowatch.com/, there are several distributions whose names could be mentioned in service. It's a top 100 of primal distributions for 2009 year. In most cases theirs names will be the same in all derivate distributions: | |
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
|-style="background:#787878; color: white;" | |-style="background:#787878; color: white;" | ||
! Popularity | ! Popularity | ||
| − | ! Name/ | + | ! Name/Packages database |
! Package manager | ! Package manager | ||
! Sugar support | ! Sugar support | ||
Revision as of 17:32, 23 December 2009
Introduction
The purpose of this Guide is describing how to simplify process of usage, by activity developers, packages that are not included to Sugar Platform but well packaged to various GNU/Linux distributions.
Detailed description
To use native packages, they should be wrapped into services. Such services are lightweight and contain only proper information about native packages. Also having service wrappers let us collect all distro specific information in one place, because various GNU/Linux distributions could have different names for the same upstream application.
In according to http://distrowatch.com/, there are several distributions whose names could be mentioned in service. It's a top 100 of primal distributions for 2009 year. In most cases theirs names will be the same in all derivate distributions:
| Popularity | Name/Packages database | Package manager | Sugar support |
|---|---|---|---|
| 2 | fedora | RPM (yum) | |
| 5 | debian | DEB | |
| 6 | mandriva | RPM (urpmi) | |
| 7 | puppy | PET | |
| 10 | arch | Pacman | |
| 13 | slackware | TXZ | |
| 38 | moblin | RPM | |
| 40 | frugalware | FPM (TAR.BZ2) | |
| 41 | pardus | PiSi | |
| 74 | alt | RPM (APT) | |
| 89 | turbolinux | RPM | |
| 91 | crux | TAR.GZ | |
| 96 | linuxconsole | LCM | |
| 99 | yoper | RPM |