5,705
edits
Changes
Jump to navigation
Jump to search
Line 13:
Line 13: − + − + + − + − + − + − + +
Platform Team/Guide/Sweets Packaging (view source)
Revision as of 05:17, 24 December 2009
, 05:17, 24 December 2009→Detailed description
The result for service development process will be regular 0install files that are placed to subdirectory on http://download.sugarlabs.org/services/ with name which is identity for the service in the rest of 0sugar infrastructure:
The result for service development process will be regular 0install files that are placed to subdirectory on http://download.sugarlabs.org/services/ with name which is identity for the service in the rest of 0sugar infrastructure:
* [http://download.sugarlabs.org/services/toolkit/feed.xml feed.xml], regular 0install feed file
* [http://download.sugarlabs.org/services/toolkit/runtime.xml runtime.xml], regular 0install feed file which will be used as a runtime dependency
* bunch of tarballs with sources and binaries, feed.xml contains links to these files
* [http://download.sugarlabs.org/services/toolkit/buildtime.xml buildtime.xml], regular 0install feed file which will be used as a buildtime dependency
* bunch of tarballs with sources and binaries, feed files contain links to these files
Feed file [http://download.sugarlabs.org/services/toolkit/feed.xml feed.xml], in addition to several information fields, contains ''<implementation>'' tag which describes implementation of the service, in distribution terms, package. At the same time, feed file could contain various implementations for various service versions. More over the same version could be represented by several implementations:
Feed files, in addition to several information fields, contains tags that describe implementations of the service, in distribution terms, package. At the same time, feed file could contain various implementations for various service versions. More over the same version could be represented by several implementations:
* source implementation, with links to source tarball and instructions how to build it
* source implementation in ''<implementation>'' tag, with links to source tarball and instructions how to build it
* no arch implementation, which can be used as-is on different platforms e.g. pure python services
* no arch implementation in ''<implementation>'' tag, which can be used as-is on different platforms e.g. pure python services
* one or several binary implementations, that contain binaries for the same source implementation but for various dependency environments(e.g. f9 could contain different versions for the same service dependency in comparing with f11)
* one or several binary implementations in ''<implementation>'' tags, that contain binaries for the same source implementation but for various dependency environments(e.g. f9 could contain different versions for the same service dependency in comparing with f11)
* package implementation in ''<package-implementation>'' tag, to reuse native packages, see [[Documentation_Team/Services/Non_Sugar_Platform_Dependencies_Guide|Non Sugar Platform Dependencies Guide]] for more info.
== service.info file ==
== service.info file ==