5,705
edits
Changes
Platform Team/Guide/Sweets Usage (view source)
Revision as of 03:07, 2 October 2011
, 03:07, 2 October 2011→Sugar via Sweets
== Sugar via Sweets ==
== 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 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 start can be processed only in a Desktop Environment, e.g., Gnome. To launch a recent stable Sugar version in emulator mode, type in a terminal:
sweets sdk/sugar:emulator
sweets sdk/sugar:emulator
Current sugar sweets support several Sucrose versions:
* ''0.94'', stable 0.94 branch;
* ''0.92'', stable 0.92 branch;
* ''0.88'', stable 0.88 branch and Dextrose-2 patches;
* ''0.95'', development version from the trunk.
By default, recent stable version will be used. To run a particular version:
sweets sdk/sugar:emulator = 0.88
Since there is no, for now, Sweets support in the Shell to run activities as sweets, ''sdk/sugar'' sweet contains Fructose and Sugar Platform dependencies. To run Sugar Shell without them, use the ''shell'' command:
sweets sdk/sugar:shell
If you need to develop sweets you are launching, see [[Platform_Team/Guide/Sweets_Packaging#Development_with_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 new X session. Place {{Code|sweets}} invocation into your {{Code|~/.xsession}} file:
To start Sugar in the session mode, i.e., not from Xephyr, it will be useful to add new X session. Place {{Code|sweets}} invocation into your {{Code|~/.xsession}} file: