8,288
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − <noinclude>{{GoogleTrans-en}}{{TOCright}}+ − + + + − + + + + + + − + − 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.+ + + − + − + − + − + − + − + − + − + − + − + − + − + − + − |- − |17 − |gentoo − |[http://packages.gentoo.org/ portage] − |[[Community/Distributions/Gentoo|yes]] − + − + − + − + − + − + − + − + − + Line 102:
Line 106: − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Documentation Team/Obsolete/Services Wrap native packages HOWTO (view source)
Revision as of 15:13, 3 July 2012
, 15:13, 3 July 2012link updates
{{Obsolete | Was only draft content.}}
[[Category:Activity Team]]
<noinclude>
[[Category:Services/Documentation]]
</noinclude>
</noinclude>
== Introduction ==
== Introduction ==
The purpose of this Guide is describing how to simplify process of usage, by activity developers, packages that are not included to [[0.86/Platform_Components|Sugar Platform]] but well packaged to various GNU/Linux distributions.
The purpose of this Guide is to describe how to simplify the usage by activity or service developers of packages that are not included in the [[0.86/Platform_Components|Sugar Platform]] but are well packaged by various GNU/Linux distributions.
== Workflows ==
* If the service you are planing to use already exists on http://download.sugarlabs.org/services/, just add its name to the ''requires'' field in your [[Documentation Team/Services/Activity Developers Guide|activity]] or [[Documentation Team/Services/Service Developers Guide|service]] ''.info'' file.
* Otherwise, read the rest of this document to learn how to create a service that represents a native package.
== Detailed description ==
== 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.
To use native packages, they should be wrapped into services. Such services are lightweight and contain only the appropriate information about native packages. By having service wrappers, we can collect all distro-specific information in one place, because various GNU/Linux distributions could have different names for the same upstream application.
=== Prime distributions list ===
According to http://distrowatch.com/, there are several distributions whose names could be mentioned in a service. The following table is a list of primary distributions from the top 100 for year 2009 (excluding source-based and special distributions), in most cases, their names will be the same in all derivative 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 in service
! Name in service.info
! Packages
! Packages
! Sugar support
! Sugar support
|-
|-
|2
|2
|fedora
|[http://distrowatch.com/fedora fedora]
|[http://rpm.pbone.net/index.php3/stat/2/simple/2 RPM (yum)]
|[http://rpm.pbone.net/index.php3/stat/2/simple/2 RPM (yum)]
|[[Community/Distributions/Fedora|yes]]
|[[Fedora|yes]]
|-
|-
|4
|4
|suse
|[http://distrowatch.com/suse suse]
|[http://rpm.pbone.net/index.php3/stat/2/simple/2 RPM]
|[http://rpm.pbone.net/index.php3/stat/2/simple/2 RPM]
|[http://en.opensuse.org/Sugar yes]
|[http://en.opensuse.org/Sugar yes]
|-
|-
|5
|5
|debian
|[http://distrowatch.com/debian debian]
|[http://www.debian.org/distrib/packages#search_packages DEB]
|[http://www.debian.org/distrib/packages#search_packages DEB]
|[[Community/Distributions/Debian|yes]]
|[[Debian|yes]]
|-
|-
|6
|6
|mandriva
|[http://distrowatch.com/mandriva mandriva]
|[http://rpm.pbone.net/index.php3/stat/2/simple/2 RPM (urpmi)]
|[http://maint.mandriva.com/ RPM (urpmi)]
|[[Community/Distributions/Mandriva|yes]]
|[[Mandriva|yes]]
|-
|-
|7
|7
|puppy
|[http://distrowatch.com/puppy puppy]
|PET
|PET
|no
|no
|-
|-
|10
|10
|arch
|[http://distrowatch.com/arch archlinux]
|Pacman
|[http://www.archlinux.org/packages/ Pacman]
|[http://wiki.archlinux.org/index.php/Sugar yes]
|[http://wiki.archlinux.org/index.php/Sugar yes]
|-
|-
|13
|13
|slackware
|[http://distrowatch.com/slackware slackware]
|TXZ
|TXZ
|no
|no
|-
|-
|38
|38
|moblin
|[http://distrowatch.com/moblin moblin]
|RPM
|RPM
|no
|no
|-
|-
|40
|40
|frugalware
|[http://distrowatch.com/frugalware frugalware]
|FPM (TAR.BZ2)
|FPM (TAR.BZ2)
|no
|no
|-
|-
|41
|41
|pardus
|[http://distrowatch.com/pardus pardus]
|PiSi
|PiSi
|no
|no
|-
|-
|74
|74
|altlinux
|[http://distrowatch.com/altlinux altlinux]
|[http://www.sisyphus.ru:1080/en/packages/ RPM (APT)]
|[http://www.sisyphus.ru:1080/en/packages/ RPM (APT)]
|[[Community/Distributions/ALTLinux|yes]]
|[[ALT Linux|yes]]
|-
|-
|89
|89
|turbolinux
|[http://distrowatch.com/turbolinux turbolinux]
|RPM
|RPM
|no
|no
|-
|-
|91
|91
|crux
|[http://distrowatch.com/crux crux]
|TAR.GZ
|TAR.GZ
|no
|no
|-
|-
|96
|96
|linuxconsole
|[http://distrowatch.com/linuxconsole linuxconsole]
|LCM
|LCM
|no
|no
|-
|-
|99
|99
|yoper
|[http://distrowatch.com/yoper yoper]
|RPM
|RPM
|no
|no
|}
|}
== Known issue ==
Package wrappers are regular services, so read the [[Documentation_Team/Services/Service_Developers_Guide|Service Developers Guide]] first.
== service.info file ==
In addition to the [[Documentation_Team/Services/Service_Developers_Guide#service.info_file|standard]] ''service.info'' file, the wrappers' file contains the following:
* ''Service'' section contains only
** name
** summary
** description
** homepage
* It should contain one or more ''Distro:<name>'' sections
* ''Distro:'' section with name ''*'', describes common distro parameters.
Each ''Distro:'' section
* should contain a ''name'' field which is a local package name for the service,
* an optional ''buildtime-name'' field, which goes to the buildtime.xml feed, by default ''name'' will be used.
* Applications could contain a ''main'' field with a full path to the exec file (which could be different for different distributions).
== Workflow ==
* Create a [[#service.info file|service.info]] file.
* Add a ''Distro:*'' section with common distro parameters.
* Add ''Distro:<name>'' sections, at least for [[#Prime_distributions_list|sugar supported]] distributions.
* Execute ''0sugar push'' to upload changes to the server.
* If a service's application is not well packaged, please consider the possibility of [[Documentation_Team/Services/Service_Developers_Guide|adding]] source and binary service implementations.
== Known issues ==
* In RO mode (check if some package is installed), 0install can work only with deb and rpm based distributions or, if PackageKit is installed, all distributions that current PackageKit version supports.
* To install packages, the system should have PackageKit.