Sugar Labs - User contributions [en]

Platform Team/Guide/Sweets Usage

2011-01-14T20:05:48Z

Mohit nagpal:

This guide describes how to use Sugar Labs' [[Platform_Team/Doers_environment|Doers environment]] for developing core modules.

== Requirements ==

* Install PackageKit and PackageKit authentication agent from native packages. On Debian-based systems, these packages are {{Code|packagekit}} and {{Code|packagekit-gnome}} (for Gnome Desktop Environment), for fedora 13 {{code|PackageKit}}
* PackageKit authentication agent should be launched to let the {{Code|sweets}} command install dependencies. Usually it is started after being logged into a Desktop Environment session (it isn't for Sugar session).
* Download and launch our [http://download.sugarlabs.org/packages/0sugar/sweets.sh self-extracted installer].
* Installer will add {{Code|~/.local/bin}} directory to the {{Code|PATH}}. So, re-login from an X session to take into account the new {{Code|PATH}}.

== Clone the sources ==

To checkout sugar project sources:

sweets --deep clone sugar

Where {{Code|--deep}} says {{Code|sweets}} process all dependencies.

Each project will be placed into the default {{Code|~/sweets}} directory. These are regular sources clones with one exception, each project contains a [[Platform Team/Recipe Specification|sweets.recipe]] spec file.
Projects might be cloned in the regular way; {{Code|sweets clone}} is just a convenient method since some of the projects are gitorious forks.

== Launch sugar ==

To launch sugar session:

sweets sugar

or to run from Xephyr:

sweets sugar:emulator

During the first launch, sources will be built. To rebuild them at any time:

sweets -ff make ''sweet''

=== Run sweets from X session ===

Place sweets invocation into your {{Code|~/.xsession}} file:

PATH=$HOME/.local/bin:$PATH
sweets 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

== Develop ==

Cloned projects will be built according to {{Code|[Build]}} section commands in recipe files. In general, for autotools-based projects, there is no further need for the {{Code|sweets}} command, just run {{Code|make install}} to build current sources and copy them to the directory that was specified by {{Code|sweets}} in the configure stage.

For glucose projects, there is no need even in calling the {{Code|make}} command, python code will be reused from its original place (see {{Code|binding}} options in recipe files), change the code and restart sugar.

For activities, follow regular activity developing procedure - clone them to {{Code|~/Activities}} directory and run from sugar shell.

== Upgrade ==

To use testing versions, enable "Help test new versions" checkbox on:

0launch -g

To upgrade sweets itself to the recent version:

sweets -R upgrade

== Run sweets from sources ==

git clone git://git.sugarlabs.org/0sugar/sweets.git ''<install-path>''
echo 'PATH=~/.local/bin:$PATH' >> ~/.bashrc
mkdir -p ~/.local/bin
ln -fs ''<install-path>''/0run ~/.local/bin/0run
ln -fs 0run ~/.local/bin/sweets
ln -fs 0run ~/.local/bin/0launch

== Current limitations ==

* Glucose needs to be patched, thus these are gitorious forks.
* Packages cannot be built from sources without cloning.
* For now, {{Code|sweets}} knowns only about glucose dependencies to install them from native packages in Debian, Ubuntu, Fedora, Mandriva, openSUSE, and Gentoo.
* Activities can't reuse sweets benefits.

Platform Team/Guide/Sweets Usage

2011-01-14T20:04:23Z

Mohit nagpal:

This guide describes how to use Sugar Labs' [[Platform_Team/Doers_environment|Doers environment]] for developing core modules.

== Requirements ==

* Install PackageKit and PackageKit authentication agent from native packages. On Debian-based systems, these packages are {{Code|packagekit}} and {{Code|packagekit-gnome}} (for Gnome Desktop Environment), for fedora 13 - {code|PackageKit}
* PackageKit authentication agent should be launched to let the {{Code|sweets}} command install dependencies. Usually it is started after being logged into a Desktop Environment session (it isn't for Sugar session).
* Download and launch our [http://download.sugarlabs.org/packages/0sugar/sweets.sh self-extracted installer].
* Installer will add {{Code|~/.local/bin}} directory to the {{Code|PATH}}. So, re-login from an X session to take into account the new {{Code|PATH}}.

== Clone the sources ==

To checkout sugar project sources:

sweets --deep clone sugar

Where {{Code|--deep}} says {{Code|sweets}} process all dependencies.

Each project will be placed into the default {{Code|~/sweets}} directory. These are regular sources clones with one exception, each project contains a [[Platform Team/Recipe Specification|sweets.recipe]] spec file.
Projects might be cloned in the regular way; {{Code|sweets clone}} is just a convenient method since some of the projects are gitorious forks.

== Launch sugar ==

To launch sugar session:

sweets sugar

or to run from Xephyr:

sweets sugar:emulator

During the first launch, sources will be built. To rebuild them at any time:

sweets -ff make ''sweet''

=== Run sweets from X session ===

Place sweets invocation into your {{Code|~/.xsession}} file:

PATH=$HOME/.local/bin:$PATH
sweets 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

== Develop ==

Cloned projects will be built according to {{Code|[Build]}} section commands in recipe files. In general, for autotools-based projects, there is no further need for the {{Code|sweets}} command, just run {{Code|make install}} to build current sources and copy them to the directory that was specified by {{Code|sweets}} in the configure stage.

For glucose projects, there is no need even in calling the {{Code|make}} command, python code will be reused from its original place (see {{Code|binding}} options in recipe files), change the code and restart sugar.

For activities, follow regular activity developing procedure - clone them to {{Code|~/Activities}} directory and run from sugar shell.

== Upgrade ==

To use testing versions, enable "Help test new versions" checkbox on:

0launch -g

To upgrade sweets itself to the recent version:

sweets -R upgrade

== Run sweets from sources ==

git clone git://git.sugarlabs.org/0sugar/sweets.git ''<install-path>''
echo 'PATH=~/.local/bin:$PATH' >> ~/.bashrc
mkdir -p ~/.local/bin
ln -fs ''<install-path>''/0run ~/.local/bin/0run
ln -fs 0run ~/.local/bin/sweets
ln -fs 0run ~/.local/bin/0launch

== Current limitations ==

* Glucose needs to be patched, thus these are gitorious forks.
* Packages cannot be built from sources without cloning.
* For now, {{Code|sweets}} knowns only about glucose dependencies to install them from native packages in Debian, Ubuntu, Fedora, Mandriva, openSUSE, and Gentoo.
* Activities can't reuse sweets benefits.