Sugar

From ArchWiki
Revision as of 09:13, 26 June 2009 by Schivmeister (Talk | contribs) (Building a Modular Group: updated dep list)

Jump to: navigation, search


Introduction

A product of the OLPC initiative, Sugar is a Desktop Environment akin to KDE and GNOME, but geared towards children and education. If you have a young son, daughter, brother, sister, puppy or alien, the best way to introduce them to the world of Arch Linux is by deploying an Arch/Sugar platform and then forgetting about it. That's the beauty of Arch Linux (TM) - Deploy and Forget (But Know How to Deploy).

But wait..where art thou, O Sugar?

That's right. To lead such a good life, you need at least some Sugar-related packages in at least AUR.

Getting Started

I have begun noting down the dependencies, and if I do get the time to complete scripting the entire sugar group, I will put them all up on AUR as soon as I am able to.

"I hope we can remove these first-person references soon" -- schiv on himself

And yes, YOU should not be lazy and carry on independently from the information herein.

Building a Bundle

This is a cool build system provided by the developers that allows one to download and build Sugar almost in its entirety. You will be told what you need, and of course, it will not help if what you need has not yet been packaged for us mighty Archers.

The resulting project can then be offered as a bundle, but it also means that the packager should take care to properly provide for and conflict with dependencies (that already exist as packages for Arch) pulled in by this Sugar build system. If not, we will be running into quite a lot of complaints from pacman.

This method of building should not be encouraged, since it is not "modular". A likely analogy is this, although we do not have the same luxury of there already being a group in the first place. As such, we cannot have:

provides=('foobar') # as in provides=('e')

But instead:

provides=('app1' 'foobar' 'app2' 'dep1' 'dep2' 'app3' 'app4' 'dep3' 'dep4')

And conflict with all of those as well.

Building a Modular Group

This is the more appropriate route to take. Here is the current list of noted dependencies, acquired by inspecting the build trees of distributions supported by Sugar (Gentoo in particular):

# Syntax: pkgname .. location (NA="not available") + comment1 + comment2 ..

espeak			 :-> [community]
squeak			 :-> [unsupported] + outdated + needs patching for sugar
evince			 :-> [extra] + needs patching for sugar
pyabiword		 :-> [unsupported]
python-cjson		 :-> [community]
python-telepathy	 :-> [community]
gst-plugins-espeak	 :-> [unsupported]
olpcsound		 :-> [unsupported]
telepathy-glib		 :-> [community]
xulrunner		 :-> [extra]
telepathy-gabble	 :-> [community]
telepathy-salut		 :-> [community]
hippo-canvas		 :-> [unsupported]

And the bash-fu to install all existing packages (if you have saved the above in a file called sugar.todo):

~# pacman -S $(grep ":->" sugar.todo | grep -v NA | grep -v unsupported | awk '{print $1}')

The above basically filters the output, first matching a string with grep, then leaving out matches with grep -v, and finally showing only the first coloumn of the shell with awk.

The following are "Level 2" dependencies (required by the above):

abiword-devel		 :-> [unsupported] + required by pyabiword