Documentation Team/Obsolete/Services Wrap native packages HOWTO
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. Followed table is a list of primal distributions from top 100 for 2009 year, in most cases theirs names will be the same in all derivate distributions.
| Popularity | Name in service | Packages | Sugar support |
|---|---|---|---|
| 2 | fedora | RPM (yum) | yes |
| 4 | suse | RPM | yes |
| 5 | debian | DEB | yes |
| 6 | mandriva | RPM (urpmi) | yes |
| 7 | puppy | PET | no |
| 10 | arch | Pacman | yes |
| 13 | slackware | TXZ | no |
| 17 | gentoo | portage | yes |
| 38 | moblin | RPM | no |
| 40 | frugalware | FPM (TAR.BZ2) | no |
| 41 | pardus | PiSi | no |
| 74 | altlinux | RPM (APT) | yes |
| 89 | turbolinux | RPM | no |
| 91 | crux | TAR.GZ | no |
| 96 | linuxconsole | LCM | no |
| 99 | yoper | RPM | no |