Sugar has a special Taxonomy to name the parts of its system. The graphical interface itself constitute the Glucose group. This is the core system can reasonably expect to be present when installing Sugar. But to really use the environment, you need activities (some sort of applications). Base activities are part of Fructose. Then, Sucrose is constituted by both Glucose and Fructose and represents what should be distributed as a basic sugar desktop environment. Extra activities are part of Honey. Note that Ribose (the underlaying operating system) is here replaced by Arch.
With the upcoming python2 deprecation, python3-based packages have been released in an AUR. Namely the packages sugar and sugar3 distinguish between python2 and python3 packages. However, the user is free to choose between the two of them.
- For the minimal requirements to run sugar3, consider installing all the four packages, viz., broken link: package not found], AUR[broken link: package not found], AUR[broken link: package not found], AUR[broken link: package not found] AUR[
- The Sugar Python3 Activities have not been added to the sugar3 repository. You can request it at sugar-arch-repository
- For using sugar-runner on arch, install
- For the core system (Glucose), install . It provides the graphical interface and a desktop session, but not very useful on its own.
- The group contains the base activities (Fructose) including a web browser, a text editor, a media player and a terminal emulator.
- The package provides a helper script that makes it possible to launch Sugar within another desktop environment, or from the command line directly.
From Activity Library
The Sugar Activity Library provides many Activity Bundles packaged as zip files with the ".xo" extension. These bundles can be downloaded and installed to the user's directory from Sugar, but the installation does not ensure that the dependencies are satisfied. Therefore it is not the recommended way to install activities, because they likely fail to start due missing dependencies. Commonly used dependencies:
- For web activities, install from the official repositories.
- For GTK 2 based activities, install AUR from AUR.
In order to check why the activity fails to start, look at the log file located at
Sugar can be started either graphically, using a display manager, or manually from the console.
Select the session Sugar from the display manager's session menu.
Alternative method is to add
exec sugar to the
~/.xinitrc file. After that, Sugar can be launched with the
startx command (see xinitrc for additional details). After setting up the
~/.xinitrc file, it can also be arranged to Start X at login.