Documentation Team/Obsolete/Services Activity Packagers Guide - Revision history

Alsroot at 18:43, 25 November 2010

2010-11-25T18:43:40Z

← Older revision		Revision as of 14:43, 25 November 2010
Line 1:		Line 1:
			{{Obsolete \| Was only draft content.}}

	<noinclude>		<noinclude>
	{{TOCright}}		{{TOCright}}

Alsroot: moved Documentation Team/Services/Activity Packagers Guide to Documentation Team/Obsolete/Services Activity Packagers Guide

2010-11-25T18:43:23Z

moved Documentation Team/Services/Activity Packagers Guide to Documentation Team/Obsolete/Services Activity Packagers Guide

← Older revision	Revision as of 14:43, 25 November 2010
(No difference)

FGrose: work on English

2010-03-07T03:57:31Z

work on English

← Older revision		Revision as of 23:57, 6 March 2010
Line 6:		Line 6:
	== Introduction ==		== Introduction ==

	The purpose of this Guide is ~~describing~~ how to package activities that use Sugar Services.		The purpose of this Guide is to describe how to package activities that use Sugar Services.

	== Activity dependencies ==		== Activity dependencies ==

	Every activity ~~which~~ uses Sugar Services will contain additional options in activity.info file:		Every activity that uses Sugar Services will contain additional options in an activity.info file:

	* ''requires'' option, comma separated list of dependencies that should exist		* ''requires'' option, a comma-separated list of dependencies that should exist,
	* ''suggests'' option, comma separated list of dependencies that could not exist		* ''suggests'' option, a comma-separated list of dependencies that could not exist.

	Each dependency could be:		Each dependency could be a,

	* service name, the full 0install link will be http://services.sugarlabs.org/<dependency-name>		* 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		* sub service slashed name, the full 0install link will be http://services.sugarlabs.org/<dependency-name>.xml
	* full 0install link		* full 0install link.

	In any case ~~resulted~~ 0install link will contain ~~proper~~ information about dependency - home page, link to sources, licence etc.		In any case, the resulting 0install link will contain the appropriate information about dependency - home page, link to sources, licence, etc.

	~~Activity~~ itself doesn't contain any 0sugar related code, 0sugar will export ~~proper~~ environment variables to activity process e.g. PYTHONPATH or LD_LIBRARY_PATH ~~thus~~ dependencies could packaged and activity will not notice any differences between 0install dependencies and installed from packages. ~~Exception~~ is libsugarize service which exports LD_PRELOAD environment variable.		The activity itself doesn't contain any 0sugar-related code. 0sugar will export the appropriate environment variables to the activity process, e.g., PYTHONPATH or LD_LIBRARY_PATH. Thus, dependencies could be packaged and the activity will not notice any differences between 0install dependencies and those installed from packages. An exception is the libsugarize service, which exports the LD_PRELOAD environment variable.

	== Cache directory ==		== Cache directory ==

	Every activity ~~which~~ uses Sugar Services will contain .0sugar subdirectory in activity root:		Every activity that uses Sugar Services will contain a .0sugar subdirectory in its activity root

	* to keep all ~~dependencies~~ implementations (to ~~not~~ download them on demand)<br>could be any content including binaries		* to keep all necessary dependency implementations (so as not to download them on demand).<br>This could be any content, including binaries.
	* 0sugar launching code, since 0sugar is not part of Sugar Platform<br>pure python code		* 0sugar launching code, since 0sugar is not part of Sugar Platform.<br>This is pure python code.
	* .0sugar/launch script ~~that~~ starts 0sugar launching code<br>''exec'' option from activity.info invokes this script		* .0sugar/launch script, which starts 0sugar launching code<br>The ''exec'' option from activity.info invokes this script.
	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.

Alsroot: /* Introduction */

2010-02-25T09:45:46Z

Introduction

← Older revision		Revision as of 05:45, 25 February 2010
Line 6:		Line 6:
	== Introduction ==		== Introduction ==

	The purpose of this Guide is describing how to ~~use~~ package activities that use Sugar Services.		The purpose of this Guide is describing how to package activities that use Sugar Services.

	== Activity dependencies ==		== Activity dependencies ==

Cjl: moved Walter is a wanker 9/Services/Activity Packagers Guide to Documentation Team/Services/Activity Packagers Guide over redirect: revert

2010-02-25T00:15:09Z

moved Walter is a wanker 9/Services/Activity Packagers Guide to Documentation Team/Services/Activity Packagers Guide over redirect: revert

← Older revision	Revision as of 20:15, 24 February 2010
(No difference)

Faggot: moved Documentation Team/Services/Activity Packagers Guide to Walter is a wanker 9/Services/Activity Packagers Guide: Walter is a wanker

2010-02-24T23:47:40Z

moved Documentation Team/Services/Activity Packagers Guide to Walter is a wanker 9/Services/Activity Packagers Guide: Walter is a wanker

← Older revision	Revision as of 19:47, 24 February 2010
(No difference)

Alsroot: /* Cache directory */

2010-02-21T21:58:08Z

Cache directory

← Older revision		Revision as of 17:58, 21 February 2010
Line 31:		Line 31:
	* 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<br>pure python code		* 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<br>''exec'' option from activity.info invokes this script
	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.

Alsroot: /* Activity dependencies */

2010-02-21T21:46:48Z

Activity dependencies

← Older revision		Revision as of 17:46, 21 February 2010
Line 23:		Line 23:
	In any case resulted 0install link will contain proper information about dependency - home page, link to sources, licence etc.		In any case resulted 0install link will contain proper information about dependency - home page, link to sources, licence etc.

	Activity itself doesn't contain any 0sugar related code, 0sugar will export proper environment variables to activity process e.g. PYTHONPATH or LD_LIBRARY_PATH thus dependencies could packaged and activity will not notice any differences between 0install dependencies and installed from packages.		Activity itself doesn't contain any 0sugar related code, 0sugar will export proper environment variables to activity process e.g. PYTHONPATH or LD_LIBRARY_PATH thus dependencies could packaged and activity will not notice any differences between 0install dependencies and installed from packages. Exception is libsugarize service which exports LD_PRELOAD environment variable.

	== Cache directory ==		== Cache directory ==

Alsroot: /* Activity dependencies */

2010-02-21T21:44:39Z

Activity dependencies

← Older revision		Revision as of 17:44, 21 February 2010
Line 21:		Line 21:
	* full 0install link		* full 0install link

	In any case resulted 0install link will contain proper information dependency - home page, link to sources, licence etc.		In any case resulted 0install link will contain proper information about dependency - home page, link to sources, licence etc.

	Activity itself doesn't contain any 0sugar related code, 0sugar will export proper environment variables to activity process e.g. PYTHONPATH or LD_LIBRARY_PATH thus dependencies could packaged and activity will not notice any differences between 0install dependencies and installed from packages.		Activity itself doesn't contain any 0sugar related code, 0sugar will export proper environment variables to activity process e.g. PYTHONPATH or LD_LIBRARY_PATH thus dependencies could packaged and activity will not notice any differences between 0install dependencies and installed from packages.

Alsroot: /* Activity dependencies */

2010-02-21T21:43:22Z

Activity dependencies

← Older revision		Revision as of 17:43, 21 February 2010
Line 22:		Line 22:

	In any case resulted 0install link will contain proper information dependency - home page, link to sources, licence etc.		In any case resulted 0install link will contain proper information dependency - home page, link to sources, licence etc.

			Activity itself doesn't contain any 0sugar related code, 0sugar will export proper environment variables to activity process e.g. PYTHONPATH or LD_LIBRARY_PATH thus dependencies could packaged and activity will not notice any differences between 0install dependencies and installed from packages.

	== Cache directory ==		== Cache directory ==