Line 16: |
Line 16: |
| The result for service development process will be regular 0install files that are placed to subdirectory on http://services.sugarlabs.org/ with name which is identity for the service in the rest of 0sugar infrastructure. Service's subdirectory will contain: | | The result for service development process will be regular 0install files that are placed to subdirectory on http://services.sugarlabs.org/ with name which is identity for the service in the rest of 0sugar infrastructure. Service's subdirectory will contain: |
| | | |
− | * [http://download.sugarlabs.org/services/toolkit/runtime.xml runtime.xml], regular 0install feed file which will be used as a runtime dependency | + | * several .xml files that are regular 0install feeds, service.xml is the main feed for service, other feed files are optional and represent sub services e.g. [http://download.sugarlabs.org/services/toolkit/] |
− | * [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 | | * bunch of tarballs with sources and binaries, feed files contain links to these files |
| | | |
− | Feed files, in addition to several information fields, contain tags that describe implementations of the service(i.e. releases). At the same time, feed file contains implementations for various service versions and the same version could be represented by several implementations:
| + | See 0install [http://0install.net/interface-spec.html documentation] to know more about feeds. |
| | | |
− | * source implementation in ''<implementation>'' tag with attribute ''arch'' == ''*-src'', with links to source tarball and instructions how to build it
| + | Sugar Services maintainer process is using [[0sugar_tool|0sugar]] tool to create proper feeds and tarballs. |
− | * no arch implementation in ''<implementation>'' tag with attribute ''arch'' == ''*-*'', which can be used as-is on different platforms e.g. pure python services
| |
− | * one or several binary implementations in ''<implementation>'' tags, that contain binaries of the same source implementation but for various architectures(attribute ''arch'')
| |
− | * package implementation in ''<package-implementation>'' tag, to reuse native packages, see [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] for more info.
| |
| | | |
| == 0sugar tool == | | == 0sugar tool == |