Platform Team/Guide/Sweets Usage - Revision history

Alsroot: /* Current limitations */ PK on Gentoo is mostly uselss dueto USE flags

2011-12-06T17:13:43Z

Current limitations: PK on Gentoo is mostly uselss dueto USE flags

← Older revision		Revision as of 13:13, 6 December 2011
Line 123:		Line 123:
	== Current limitations ==		== Current limitations ==

	* For now, {{Code\|sweets}} knows only enough about the glucose dependencies to install them from native packages in Debian, Ubuntu, Fedora, Mandriva, openSUSE~~, and Gentoo~~.		* For now, {{Code\|sweets}} knows only enough about the glucose dependencies to install them from native packages in Debian, Ubuntu, Fedora, Mandriva, openSUSE.
	* Activities can't reuse sweets benefits.		* Activities can't reuse sweets benefits.

Alsroot: /* Required packages */

2011-12-06T13:05:57Z

Required packages

← Older revision		Revision as of 09:05, 6 December 2011
Line 12:		Line 12:
	sudo yum install gnome-packagekit		sudo yum install gnome-packagekit

	Debian and Ubuntu (starting from 11.10) specific instructions:		Debian and Ubuntu (starting from 11.10) based distributions specific instructions:

	sudo apt-get install gnome-packagekit		sudo apt-get install gnome-packagekit

	Ubuntu (before 11.10) specific instructions:		Ubuntu (before 11.10) based distributions specific instructions:

	sudo apt-get install packagekit-gnome		sudo apt-get install packagekit-gnome

Alsroot: Once more, Ubuntu people are crazy

2011-12-06T12:58:48Z

Once more, Ubuntu people are crazy

← Older revision		Revision as of 08:58, 6 December 2011
Line 12:		Line 12:
	sudo yum install gnome-packagekit		sudo yum install gnome-packagekit

	Debian and Ubuntu specific ~~instructons~~:		Debian and Ubuntu (starting from 11.10) specific instructions:

			sudo apt-get install gnome-packagekit

			Ubuntu (before 11.10) specific instructions:

	sudo apt-get install packagekit-gnome		sudo apt-get install packagekit-gnome

FGrose at 19:40, 3 December 2011

2011-12-03T19:40:29Z

← Older revision		Revision as of 15:40, 3 December 2011
Line 19:		Line 19:
	=== Install ===		=== Install ===

	~~Type~~ in Terminal activity, or any other terminal:		Enter in the Terminal activity, or any other terminal:

	wget http://download.sugarlabs.org/sweets/sweets/installer.sh		wget http://download.sugarlabs.org/sweets/sweets/installer.sh
Line 26:		Line 26:
	Relogin from X session to take into account the new PATH environment variable value.		Relogin from X session to take into account the new PATH environment variable value.

	~~Besides~~, {{Code\|sweets}} might be run from the [[Platform_Team/Guide/Sweets_Packaging#Run_Sweets_from_sources\|sources]].		Alternatively, {{Code\|sweets}} might be run from the [[Platform_Team/Guide/Sweets_Packaging#Run_Sweets_from_sources\|sources]].

	=== Upgrade ===		=== Upgrade ===

	~~Type~~ in Terminal activity, or any other terminal:		Enter in the Terminal activity, or any other terminal:

	sweets upgrade		sweets upgrade

Alsroot: /* Usage */

2011-12-03T17:57:26Z

Usage

← Older revision		Revision as of 13:57, 3 December 2011
Line 42:		Line 42:
	* {{Code\|''VERSION''}}, ''sweet'''s version		* {{Code\|''VERSION''}}, ''sweet'''s version

	See the [[Platform_Team/Guide/Sugar_via_Sweets]] guide for real examples of how to use ''Sweets'' to run Sugar Shell.		See the [[Platform_Team/Guide/Sugar_via_Sweets\|Sugar via Sweets]] guide for real examples of how to use ''Sweets'' to run Sugar Shell.

	=== Launch ===		=== Launch ===

Alsroot: Reuse "Sugar via Sweets" guide

2011-12-03T17:56:57Z

Reuse "Sugar via Sweets" guide

@@ Line 42: / Line 42: @@
 * {{Code|''VERSION''}}, ''sweet'''s version
-See the [[#Sugar_via_Sweets|Sugar via Sweets]] section for real examples of how to use ''Sweets'' to run Sugar Shell.
+See the [[Platform_Team/Guide/Sugar_via_Sweets]] guide for real examples of how to use ''Sweets'' to run Sugar Shell.
 === Launch ===
@@ Line 115: / Line 115: @@
 {{Code|sweets}} support additional notation for exact searching in the form of {{Code|''prefix''<nowiki>:=</nowiki>''string''}}. For example the query {{Code|name<nowiki>:=</nowiki>sugar}} will find ''sweet''s only with exactly {{Code|sugar}} as a name and omit names like {{Code|sugar-base}}. If the search string contains spaces, wrap it within double quotes, {{Code|name<nowiki>:=</nowiki>"Sugar Commander"}}. Note, wildcards do not work in the exact search case where asterisks will be treated literally.
 == Current limitations ==

Alsroot: /* Installation */

2011-12-03T13:57:25Z

Installation

← Older revision		Revision as of 09:57, 3 December 2011
Line 19:		Line 19:
	=== Install ===		=== Install ===

	~~Enter~~ in Terminal activity, or any other terminal:		Type in Terminal activity, or any other terminal:

	wget http://download.sugarlabs.org/sweets/sweets/installer.sh		wget http://download.sugarlabs.org/sweets/sweets/installer.sh
Line 30:		Line 30:
	=== Upgrade ===		=== Upgrade ===

	~~Enter~~ in Terminal activity, or any other terminal:		Type in Terminal activity, or any other terminal:

	sweets upgrade		sweets upgrade

Alsroot: /* Installation */

2011-12-03T13:50:49Z

Installation

← Older revision		Revision as of 09:50, 3 December 2011
Line 19:		Line 19:
	=== Install ===		=== Install ===

	Enter in Terminal activity, or any ~~over~~ terminal:		Enter in Terminal activity, or any other terminal:

	wget http://download.sugarlabs.org/sweets/sweets/installer.sh		wget http://download.sugarlabs.org/sweets/sweets/installer.sh
Line 30:		Line 30:
	=== Upgrade ===		=== Upgrade ===

	Enter in Terminal activity, or any ~~over~~ terminal:		Enter in Terminal activity, or any other terminal:

	sweets upgrade		sweets upgrade

Alsroot: /* Installation */ Update Upgrade section after removing install-from-source option

2011-12-03T13:38:21Z

Installation: Update Upgrade section after removing install-from-source option

← Older revision		Revision as of 09:38, 3 December 2011
Line 18:		Line 18:

	=== Install ===		=== Install ===

			Enter in Terminal activity, or any over terminal:

	wget http://download.sugarlabs.org/sweets/sweets/installer.sh		wget http://download.sugarlabs.org/sweets/sweets/installer.sh
Line 28:		Line 30:
	=== Upgrade ===		=== Upgrade ===

	~~If sweets was installed from a bundle~~:		Enter in Terminal activity, or any over terminal:

	sweets upgrade		sweets upgrade

Alsroot: /* Usage */ Make command-line arguments more exposed

2011-12-03T13:18:13Z

Usage: Make command-line arguments more exposed

← Older revision		Revision as of 09:18, 3 December 2011
Line 36:		Line 36:
	Read the [[Platform_Team/Sweets/Glossary\|Sweets Glossary]] to understand the basic concept (and [[Platform_Team/Infrastructure\|overview]] of the bigger picture). The rest of the text will operate with the following terms:		Read the [[Platform_Team/Sweets/Glossary\|Sweets Glossary]] to understand the basic concept (and [[Platform_Team/Infrastructure\|overview]] of the bigger picture). The rest of the text will operate with the following terms:

	* {{Code\|SWEET}}, the full ''interface'' URL, like {{Code\|http://sweets.sugarlabs.org/sdk/sugar}}, or the short one, like {{Code\|sdk/sugar}};		* {{Code\|''SWEET''}}, the full ''interface'' URL, like {{Code\|http://sweets.sugarlabs.org/sdk/sugar}}, or the short one, like {{Code\|sdk/sugar}};
	* {{Code\|COMMAND}}, ''sweet'''s command that indicates how to run a particular ''sweet''; by default, ''sweet''s have only the {{Code\|run}} command, but it is possible to have several commands;		* {{Code\|''COMMAND''}}, ''sweet'''s command that indicates how to run a particular ''sweet''; by default, ''sweet''s have only the {{Code\|run}} command, but it is possible to have several commands;
	* {{Code\|VERSION}}, ''sweet'''s version		* {{Code\|''VERSION''}}, ''sweet'''s version

	See the [[#Sugar_via_Sweets\|Sugar via Sweets]] section for real examples of how to use ''Sweets'' to run Sugar Shell.		See the [[#Sugar_via_Sweets\|Sugar via Sweets]] section for real examples of how to use ''Sweets'' to run Sugar Shell.
Line 46:		Line 46:
	To launch a ''sweet'' with verbatim passing of optional {{Code\|ARGUMENTS}}:		To launch a ''sweet'' with verbatim passing of optional {{Code\|ARGUMENTS}}:

	sweets SWEET [ARGUMENTS]		sweets ''<SWEET>'' [''<ARGUMENTS>'']

	Sometimes ''sweet''s support several launching commands; it is possible to specify one during the launch:		Sometimes ''sweet''s support several launching commands; it is possible to specify one during the launch:

	sweets SWEET:COMMAND		sweets ''<SWEET>'':''<COMMAND>''

	To run a particular, but not the latest, version:		To run a particular, but not the latest, version:

	sweets SWEET ''=''\|''>=''\|''<='' VERSION		sweets ''<SWEET>'' ''=''\|''>=''\|''<='' ''<VERSION>''

	To get the full list of available versions:		To get the full list of available versions:

	sweets status SWEET -v		sweets status ''<SWEET>'' -v

	To get information, e.g., a list of supported commands, about a ''sweet'':		To get information, e.g., a list of supported commands, about a ''sweet'':

	sweets show SWEET		sweets show ''<SWEET>''

	=== Troubleshooting ===		=== Troubleshooting ===
Line 72:		Line 72:
	''Feeds'' are being updated from time to time. After experiencing any problems, and for refreshing the local ''feeds'' cache, it will be useful to re-download ''feeds''. Use, once, the {{Code\|-R}} command line argument for the launch command (make sure that {{Code\|-R}} goes before the {{Code\|SWEET}}, because using it afterwards will cause passing it as a {{Code\|SWEET}}'s argument):		''Feeds'' are being updated from time to time. After experiencing any problems, and for refreshing the local ''feeds'' cache, it will be useful to re-download ''feeds''. Use, once, the {{Code\|-R}} command line argument for the launch command (make sure that {{Code\|-R}} goes before the {{Code\|SWEET}}, because using it afterwards will cause passing it as a {{Code\|SWEET}}'s argument):

	sweets -R SWEET		sweets -R ''<SWEET>''

	'''Analyze dependencies tree'''		'''Analyze dependencies tree'''
Line 78:		Line 78:
	If {{Code\|sweets}} can't find a proper ''implementation'', see the {{Code\|e}} lines in the output of:		If {{Code\|sweets}} can't find a proper ''implementation'', see the {{Code\|e}} lines in the output of:

	sweets status SWEET -vdd		sweets status ''<SWEET>'' -vdd

	'''Keep the system in consistent state'''		'''Keep the system in consistent state'''
Line 90:		Line 90:
	For command format is:		For command format is:

	sweets search QUERY		sweets search ''<QUERY>''

	Notice that [http://xapian.org/docs/queryparser.html#partially-entered-query-matching partial] search is enabled. So, the query {{Code\|tele}} will be treated as {{Code\|tele*}} to search all words that start from {{Code\|tele}}.		Notice that [http://xapian.org/docs/queryparser.html#partially-entered-query-matching partial] search is enabled. So, the query {{Code\|tele}} will be treated as {{Code\|tele*}} to search all words that start from {{Code\|tele}}.