Platform Team/Guide/Sweets Usage: Difference between revisions
No edit summary |
→Requirements: a typo |
||
| Line 4: | Line 4: | ||
* 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). | * 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). | ||
* PackageKit authentication agent should be launched to let the {{Code|sweets}} command install dependencies. Usually it is started after being logged into a | * 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]. | * 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}}. | * 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}}. | ||