Difference between revisions of "Documentation Team/Obsolete/Services Activity Packagers Guide"
Jump to navigation
Jump to search
(Created page with '<noinclude> {{TOCright}} Category:Services/Documentation </noinclude> == Introduction == The purpose of this Guide is describing how to use package activities that use Suga…') |
|||
| Line 28: | Line 28: | ||
* to keep all dependencies implementations (to not download them on demand)<br>could be any content including binaries | * 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< | + | * 0sugar launching code, since 0sugar is not part of Sugar Platform<br>pure python code |
* .0sugar/launch script that starts 0sugar launching code | * .0sugar/launch script that starts 0sugar launching code | ||
exec $(dirname $0)/<path-to-0sugar>/0sugar-selector "$@" | exec $(dirname $0)/<path-to-0sugar>/0sugar-selector "$@" | ||
If all dependencies(including 0sugar) are packaged then this directory could be just removed. | If all dependencies(including 0sugar) are packaged then this directory could be just removed. | ||
Revision as of 17:32, 21 February 2010
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)
could be any content including binaries - 0sugar launching code, since 0sugar is not part of Sugar Platform
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.