Platform Team/Guide/Sweets Usage: Difference between revisions

Line 1:

This guide describes how to use Sugar Labs' Packaging Management System.

== ~~Requirements~~ ==

== Installation ==

=== Required packages ===

At first, install PackageKit related packages. The following command will install two Polkit authentication agents, one for Gnome session (if you start sugar emulator from Gnome Desktop Environment) and LXPolkit that will be used from Sugar session.

* 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~~, {{code|PackageKit}} and {{Code|~~gnome-packagekit~~}}.~~

Fedora specific instructions:

sudo yum install gnome-packagekit lxpolkit

* 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~~).

Debian and Ubuntu specific instructons (there is no official package for LXPolkit?):

sudo apt-get install packagekit-gnome

== ~~Installation~~ ==

Relogin from X session to let Gnome or Sugar start Polkit authentication agent.

=== Bundle install ===

wget http://download.sugarlabs.org/sweets/sweets/installer.sh

sh installer.sh

Relogin from X session to take into account new PATH environment variable value.

=== Sources install ===

This will be useful for people who prefer using sources.

* Clone sweets sources and install it (after the first run, you need to relogin to take into account the new PATH value, then just run {{Code|sweets}} command):

Line 14:

Line 31:

sweets/sweets upgrade

* If sweets ~~sources were already cloned, pull new changes~~ from ~~cloned directory~~:

=== Upgrade ===

If sweets was installed from a bundle:

sweets upgrade

If sweets is being used from sources, pull new commits from cloned directory:

git --recurse-submodules pull origin master

* '''TODO''' more easy installation for non-tech people

== Launch sugar ==

Line 33:

Line 52:

sweets sdk/sugar:emulator=0.88

To get the full list of available versions:

sweets show sdk/sugar -v

For launch command, all arguments passed after sweet name are treated as launched sweet's arguments. For example, it is possible to run sugar by bassing {{Code|-f}} argument:

sweets sdk/sugar:emulator=0.88 -f

If sweets can't find proper implementation, see the {{Code|E}} lines in output of:

sweets show sdk/sugar -vdd

== Development workflow with sweets ==

@@ Line 1: / Line 1: @@
 This guide describes how to use Sugar Labs' Packaging Management System.
-== Requirements ==
+== Installation ==
+=== Required packages ===
+At first, install PackageKit related packages. The following command will install two Polkit authentication agents, one for Gnome session (if you start sugar emulator from Gnome Desktop Environment) and LXPolkit that will be used from Sugar session.
-* 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, {{code|PackageKit}} and {{Code|gnome-packagekit}}.
+Fedora specific instructions:
+ sudo yum install gnome-packagekit lxpolkit
-* 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).
+Debian and Ubuntu specific instructons (there is no official package for LXPolkit?):
+ sudo apt-get install packagekit-gnome
-== Installation ==
+Relogin from X session to let Gnome or Sugar start Polkit authentication agent.
+=== Bundle install ===
+ wget http://download.sugarlabs.org/sweets/sweets/installer.sh
+ sh installer.sh
+Relogin from X session to take into account new PATH environment variable value.
+=== Sources install ===
+This will be useful for people who prefer using sources.
 * Clone sweets sources and install it (after the first run, you need to relogin to take into account the new PATH value, then just run {{Code|sweets}} command):
@@ Line 14: / Line 31: @@
   sweets/sweets upgrade
-* If sweets sources were already cloned, pull new changes from cloned directory:
+=== Upgrade ===
+If sweets was installed from a bundle:
+ sweets upgrade
+If sweets is being used from sources, pull new commits from cloned directory:
   git --recurse-submodules pull origin master
-* '''TODO''' more easy installation for non-tech people
 == Launch sugar ==
@@ Line 33: / Line 52: @@
   sweets sdk/sugar:emulator=0.88
+To get the full list of available versions:
+ sweets show sdk/sugar -v
 For launch command, all arguments passed after sweet name are treated as launched sweet's arguments. For example, it is possible to run sugar by bassing {{Code|-f}} argument:
   sweets sdk/sugar:emulator=0.88 -f
+If sweets can't find proper implementation, see the {{Code|E}} lines in output of:
+ sweets show sdk/sugar -vdd
 == Development workflow with sweets ==