Difference between revisions of "Platform Team/Guide/Sweets Packaging"

From Sugar Labs
Jump to navigation Jump to search
Line 23: Line 23:
 
== Detailed description ==
 
== Detailed description ==
  
The resulting service development process will consist of regular 0install files that are placed in a subdirectory on http://services.sugarlabs.org/ with a name that is the identity for the service in the rest of the 0sugar infrastructure. Service's subdirectory will contain:
+
The resulting service development process will consist of regular 0install files that are placed in a subdirectory on http://services.sugarlabs.org/ with a name that is the identity for the service in the rest of the 0sugar infrastructure. The Service's subdirectory will contain:
  
 
* Several .xml files that are regular 0install feeds. service.xml is the main feed for the service, other feed files are optional and represent sub services, e.g., [http://download.sugarlabs.org/services/toolkit/].
 
* Several .xml files that are regular 0install feeds. service.xml is the main feed for the service, other feed files are optional and represent sub services, e.g., [http://download.sugarlabs.org/services/toolkit/].
Line 41: Line 41:
 
  http://services.sugarlabs.org/<service>/<subservice>.xml
 
  http://services.sugarlabs.org/<service>/<subservice>.xml
  
To start Sugar Services developing process:
+
To start the Sugar Services developing process:
* Install [[Documentation_Team/Services/0sugar|0sugar]] tool
+
* Install the [[Documentation_Team/Services/0sugar|0sugar]] tool.
* Read ''service.info'' file [[Documentation_Team/Services/Service.info_Specification|specification]]
+
* Read ''service.info'' file.
 +
[[Documentation_Team/Services/Service.info_Specification|specification]]
 
and follow the rest of this document instruction about development details.
 
and follow the rest of this document instruction about development details.
  

Revision as of 21:24, 20 July 2010

Pitfalls

Devel packages

It is common practice in binary based GNU/Linux distributions to use satellite devel packages to collect various build time files like C headers of pkg-config files. In 0install environment it doesn't work, because every package is stored in separate directory hierarchy, e.g., *.so symlinks, from devel package, will point to nothing since all *.so.* files from library package live in separate directory.

Keep all build time files in runtime package.