Platform Team/Guide/Sweets Usage: Difference between revisions
No edit summary |
|||
| Line 6: | Line 6: | ||
* 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). | * 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). | ||
== Installation == | |||
* 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): | * 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 11: | Line 13: | ||
git clone --recursive git://git.sugarlabs.org/sdk/sweets.git | git clone --recursive git://git.sugarlabs.org/sdk/sweets.git | ||
sweets/sweets upgrade | sweets/sweets upgrade | ||
* If sweets sources were already cloned, pull new changes from cloned directory: | |||
git --recurse-submodules pull origin master | |||
* '''TODO''' more easy installation for non-tech people | |||
== Launch sugar == | == Launch sugar == | ||