Difference between revisions of "Documentation Team/Obsolete/Services Wrap native packages HOWTO"
Jump to navigation
Jump to search
m (link updates) |
|||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Obsolete | Was only draft content.}} | |
| − | [[Category: | + | |
| + | <noinclude> | ||
| + | [[Category:Services/Documentation]] | ||
</noinclude> | </noinclude> | ||
== Introduction == | == Introduction == | ||
| − | The purpose of this Guide is | + | 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 == | == Workflows == | ||
| − | * If service | + | * 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 | + | 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;" | ||
| Line 30: | Line 32: | ||
|[http://distrowatch.com/fedora 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)] | ||
| − | |[[ | + | |[[Fedora|yes]] |
|- | |- | ||
|4 | |4 | ||
| Line 40: | Line 42: | ||
|[http://distrowatch.com/debian debian] | |[http://distrowatch.com/debian debian] | ||
|[http://www.debian.org/distrib/packages#search_packages DEB] | |[http://www.debian.org/distrib/packages#search_packages DEB] | ||
| − | |[[ | + | |[[Debian|yes]] |
|- | |- | ||
|6 | |6 | ||
|[http://distrowatch.com/mandriva mandriva] | |[http://distrowatch.com/mandriva mandriva] | ||
|[http://maint.mandriva.com/ RPM (urpmi)] | |[http://maint.mandriva.com/ RPM (urpmi)] | ||
| − | |[[ | + | |[[Mandriva|yes]] |
|- | |- | ||
|7 | |7 | ||
| Line 80: | Line 82: | ||
|[http://distrowatch.com/altlinux altlinux] | |[http://distrowatch.com/altlinux altlinux] | ||
|[http://www.sisyphus.ru:1080/en/packages/ RPM (APT)] | |[http://www.sisyphus.ru:1080/en/packages/ RPM (APT)] | ||
| − | |[[ | + | |[[ALT Linux|yes]] |
|- | |- | ||
|89 | |89 | ||
| Line 104: | Line 106: | ||
|} | |} | ||
| − | Package wrappers are regular services, so read [[Documentation_Team/Services/Service_Developers_Guide|Service Developers Guide]] first. | + | Package wrappers are regular services, so read the [[Documentation_Team/Services/Service_Developers_Guide|Service Developers Guide]] first. |
== service.info file == | == service.info file == | ||
| − | In addition to [[Documentation_Team/Services/Service_Developers_Guide#service.info_file|standard]] ''service.info'' file, wrappers' 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 | * ''Service'' section contains only | ||
| Line 115: | Line 117: | ||
** description | ** description | ||
** homepage | ** homepage | ||
| − | * should contain one or more ''Distro:<name>'' sections | + | * It should contain one or more ''Distro:<name>'' sections |
| − | * ''Distro:'' section with name ''*'', describes common distro parameters | + | * ''Distro:'' section with name ''*'', describes common distro parameters. |
| − | Each ''Distro:'' section | + | Each ''Distro:'' section |
| − | * should contain ''name'' field which is local package name for service | + | * should contain a ''name'' field which is a local package name for the service, |
| − | * optional ''buildtime-name'' field which goes to buildtime.xml feed, by default ''name'' will be used | + | * 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 == | == 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 | + | == 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. |
Latest revision as of 14:13, 3 July 2012
IntroductionThe 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 Sugar Platform but are well packaged by various GNU/Linux distributions. Workflows
Detailed descriptionTo 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 listAccording 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.
Package wrappers are regular services, so read the Service Developers Guide first. service.info fileIn addition to the standard service.info file, the wrappers' file contains the following:
Each Distro: section
Workflow
Known issues
|
