James Cameron
2453d13b03
Ensure environment variables needed by Python activities are available in each of the three supported scenarios; - started from Sugar, - started from Terminal inside Sugar, - started by other desktop environments. Variables always available are; SUGAR_ACTIVITY_ROOT SUGAR_BUNDLE_ID SUGAR_BUNDLE_NAME SUGAR_BUNDLE_PATH SUGAR_BUNDLE_VERSION Variables also available when started from Sugar are; SUGAR_ACTIVITIES_HIDDEN SUGAR_APISOCKET_KEY SUGAR_APISOCKET_PORT SUGAR_GROUP_LABELS SUGAR_HOME SUGAR_MIME_DEFAULTS SUGAR_PROFILE SUGAR_SCALING SUGAR_VERSION Variables also available when started from Terminal are; SUGAR_TERMINAL_VERSION Other changes; - use os.makedirs in place of distutils.dir_util.mkpath, - avoid redundant setting of SUGAR_BUNDLE_PATH, - do not set SUGAR_BUNDLE_ID unnecessarily, - add explanatory comment, Tested on Ubuntu 18.04. Signed-off-by: James Cameron <quozl@laptop.org>
Sugar Toolkit
Sugar Toolkit provides services and a set of GTK+ widgets to build activities and other Sugar components on Linux based computers.
This is the GTK+ 3 binding of the Sugar Toolkit.
Installing on Debian or Ubuntu
Automatically done when you install Sugar desktop.
To install Sugar Toolkit alone without Sugar desktop,
sudo apt install python-sugar3
Installing on Fedora
Automatically done when you install Sugar desktop.
To install Sugar Toolkit alone without Sugar desktop,
sudo dnf install sugar-toolkit-gtk3
Building
Sugar Toolkit follows the GNU Coding Standards.
Install all dependencies, especially sugar-artwork and sugar-datastore.
Clone the repository, run autogen.sh, then make and make install.