Sugar Labs

Platform Team/Guide/Sweets Usage: Difference between revisions

← Older edit
→Current limitations: PK on Gentoo is mostly uselss dueto USE flags
 
(6 intermediate revisions by 2 users not shown)
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) based distributions specific instructions:
 
sudo apt-get install gnome-packagekit
 
Ubuntu (before 11.10) based distributions specific instructions:
 
  sudo apt-get install packagekit-gnome
  sudo apt-get install packagekit-gnome


Line 19: Line 24:
=== Install ===
=== Install ===


Enter 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 31:
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 ===


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


  sweets upgrade
  sweets upgrade
Line 42: Line 47:
* {{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 [[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]] guide for real examples of how to use ''Sweets'' to run Sugar Shell.


=== Launch ===
=== Launch ===
Line 115: Line 120:


{{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.
{{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.
== Sugar via Sweets ==
To try Sweets in practice, run several Sugar versions. On the Sweets level, there are not any restrictions to using Sweets on any GNU/Linux distribution. Successful usage depends only on the presence of PackageKit and the quality of the sweet packages (sweets). For now, sugar sweets are well aware of Fedora, Debian/Ubuntu, and Gentoo package names and not so well aware of openSUSE and Mandriva. Sugar sweets launchs were tested on some recent Fedora and Ubuntu releases. The quality of other GNU/Linux distribution support depends only on how often Sweets is used on these distributions and the reporting of problems by the community.
Note, Sugar Shell does not start the authentication agent, and preparing sugar to start can be processed only in a Desktop Environment, e.g., Gnome (or launch authentication agent manually).
There are two sweets for Glucose:
* {{Code|sdk/sugar}}, for pristine Glucose;
* {{Code|dextrose/sugar}}, for Glucose with [[Dextrose]] patches applied.
To see what Glucose versions these sweets provide, type in a terminal:
  sweets status sdk/sugar -v
To launch a recent stable Sugar version in emulator mode, type in a terminal:
sweets sdk/sugar:emulator
By default, the most recent stable version will be used. To run a particular version, execute with additional arguments:
sweets sdk/sugar:emulator = 0.88
For now, since there is no Sweets support in the Shell to run activities as sweets, Glucose sweets contain Fructose and Sugar Platform dependencies as suggested ones. To run Sugar with injection of all suggested dependencies, use the {{Code|-S<nowiki>|</nowiki>--force-suggested}} command-line argument:
sweets -S sdk/sugar:emulator
If you need to develop Sugar, see [[Platform_Team/Guide/Sweets_Packaging#Sugar_sweets|Sweets Packaging]] guide's instructions.
=== Sugar sweet from X sessions ===
To start Sugar in the session mode, i.e., not from Xephyr, it will be useful to add a new X session. Place {{Code|sweets}} invocation into your {{Code|~/.xsession}} file:
PATH=$HOME/.local/bin:$PATH
sweets sdk/sugar
and create a {{Code|/usr/share/xsessions/sweets.desktop}} desktop file:
[Desktop Entry]
Encoding=UTF-8
Name=Sweets
GenericName=Sweets
Exec=/etc/X11/Xsession
Type=Application
After getting a login screen, Sweets session should be present in the sessions list.


== 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.


Retrieved from "https://wiki.sugarlabs.org/go/Platform_Team/Guide/Sweets_Usage"