5,705
edits
Changes
Jump to navigation
Jump to search
Documentation Team/Obsolete/Services Activity Packagers Guide (view source)
Revision as of 17:32, 21 February 2010
, 17:32, 21 February 2010Created page with '<noinclude> {{TOCright}} Category:Services/Documentation </noinclude> == Introduction == The purpose of this Guide is describing how to use package activities that use Suga…'
<noinclude>
{{TOCright}}
[[Category:Services/Documentation]]
</noinclude>
== Introduction ==
The purpose of this Guide is describing how to use package activities that use Sugar Services.
== Activity dependencies ==
Every activity which uses Sugar Services will contain additional options in activity.info file:
* ''requires'' option, comma separated list of dependencies that should exist
* ''suggests'' option, comma separated list of dependencies that could not exist
Each dependency could be:
* service name, the full 0install link will be http://services.sugarlabs.org/<dependency-name>
* sub service slashed name, the full 0install link will be http://services.sugarlabs.org/<dependency-name>.xml
* full 0install link
In any case resulted 0install link will contain proper information dependency - home page, link to sources, licence etc.
== Cache directory ==
Every activity which uses Sugar Services will contain .0sugar subdirectory in activity root:
* to keep all dependencies implementations (to not download them on demand)<br>could be any content including binaries
* 0sugar launching code, since 0sugar is not part of Sugar Platform<pr>pure python code
* .0sugar/launch script that starts 0sugar launching code
exec $(dirname $0)/<path-to-0sugar>/0sugar-selector "$@"
If all dependencies(including 0sugar) are packaged then this directory could be just removed.
{{TOCright}}
[[Category:Services/Documentation]]
</noinclude>
== Introduction ==
The purpose of this Guide is describing how to use package activities that use Sugar Services.
== Activity dependencies ==
Every activity which uses Sugar Services will contain additional options in activity.info file:
* ''requires'' option, comma separated list of dependencies that should exist
* ''suggests'' option, comma separated list of dependencies that could not exist
Each dependency could be:
* service name, the full 0install link will be http://services.sugarlabs.org/<dependency-name>
* sub service slashed name, the full 0install link will be http://services.sugarlabs.org/<dependency-name>.xml
* full 0install link
In any case resulted 0install link will contain proper information dependency - home page, link to sources, licence etc.
== Cache directory ==
Every activity which uses Sugar Services will contain .0sugar subdirectory in activity root:
* to keep all dependencies implementations (to not download them on demand)<br>could be any content including binaries
* 0sugar launching code, since 0sugar is not part of Sugar Platform<pr>pure python code
* .0sugar/launch script that starts 0sugar launching code
exec $(dirname $0)/<path-to-0sugar>/0sugar-selector "$@"
If all dependencies(including 0sugar) are packaged then this directory could be just removed.