5,705
edits
Changes
Jump to navigation
Jump to search
Line 106:
Line 106: − + − sweets sdk/sugar:emulator+ + + + + + − Current sugar sweets support several Sucrose versions:+ − '''Stable'''+ − * ''0.94'', stable 0.94 branch; − * ''0.92'', stable 0.92 branch; − * ''0.88'', stable 0.88 branch and Dextrose-2 patches; − * ''0.84'', stable 0.84 branch; − '''Development'''+ − * ''0.95'', development version from the trunk. Line 125:
Line 125: − +
Platform Team/Guide/Sweets Usage (view source)
Revision as of 19:14, 21 October 2011
, 19:14, 21 October 2011→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.
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. To launch a recent stable Sugar version in emulator mode, type in a terminal:
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:
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
sweets sdk/sugar:emulator = 0.88
For now, since there is no 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:
For now, since there is no Sweets support in the Shell to run activities as sweets, Glucose sweets contain Fructose and Sugar Platform dependencies. To run Sugar Shell without them, use the ''shell'' command:
sweets sdk/sugar:shell
sweets sdk/sugar:shell