Changes

== Introduction ==

== Introduction ==

The purpose of this Guide is describing how to simplify process of usage, by activity or service 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 ==

== Workflows ==

* If service, you are planing to use, already exists on http://download.sugarlabs.org/services/ just add its name to ''requires'' field in your [[Documentation Team/Services/Activity Developers Guide|activity]] or [[Documentation Team/Services/Service Developers Guide|service]] ''.info'' file

* 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 know how to create service which represents native package

* 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.

=== Primal distributions list ===

=== Prime distributions list ===

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(excluding source based and special distributions), in most cases theirs names will be the same in all derivate distributions.

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;"

|}

|}

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

** 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.

* for applications, could contain ''main'' field with full path to exec file(could be different for different distributions)

* Applications could contain a ''main'' field with a full path to the exec file (which could be different for different distributions).

== Workflow ==

== Workflow ==

* create [[#service.info file|service.info]] file

* Create a [[#service.info file|service.info]] file.

* add ''Distro:*'' section with common distro parameters

* Add a ''Distro:*'' section with common distro parameters.

* add ''Distro:<name>'' sections at least for [[#Primal_distributions_list|sugar supported]] distributions

* Add ''Distro:<name>'' sections, at least for [[#Prime_distributions_list|sugar supported]] distributions.

* exec ''0sugar push'' to upload changes to the server

* Execute ''0sugar push'' to upload changes to the server.

* if service's application is not well packaged, please consider possibility to [[Documentation_Team/Services/Service_Developers_Guide|add]] source and binary service implementations

* 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 issue ==

== Known issues ==

* in RO mode(check if some package is installed), 0install could work only with deb and rpm based distributions or, if PackageKit is installed, all distributions that current PackageKit version supports

* 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, system should have PackageKit

* To install packages, the system should have PackageKit.