Sugar on SUSE

Installation Notes

There may still be some issues with this installation... known to work as of 6/15/06.

On OpenSUSE 10.3 following this procedure fails.

CVS on Gnome is now moved to SVN.

After installing programs required with YaST and creating a folder called 'm4' to let autogen.sh complete, ./configure failes when looking for the $MOZILLA variable on line 22323.

I have not got around this yet, has anyone else?

gecko-embed

pre-requisites

I checked out gecko embed and compiled it, but before I did that I had to install a set of packages:

1. mozilla-xulrunner: you can install it from the yast package manager
2. mozilla-nss-devel: you can't install it with the default packages on package manager, but you can download it directly from suse's online repository
3. gecko-sdk: This is the equivelent of the xulrunner-devel in fedora talk for 10.1, and you can get it from suse's online repository as well. For 10.2 and later use xulrunner-devel from YAST.
4. Had to compile avahi and install it. no details, if someone went through this recently, please update with details For 10.2 and later you can get avahi from YAST.

You need two different versions of automake installed. This is not specific to Suse, it is a general issue with sugar-jhbuild. OpenSuse 10.2 provides automake 1.9. You can install 1.7.9 from source.

compile gecko-embed

• First you need to check it out from subversion. Use the following command:

svn checkout http://svn.gnome.org/svn/gecko-embed/trunk gecko-embed

• cd into the gecko-embed folder and run autogen.sh (./autogen.sh)
• run make
• run "make install" as root (or use sudo if you're a good linux citizen)

Sugar

git-clone git://dev.laptop.org/sugar-jhbuild

cd sugar-jhbuild
git-pull
./sugar-jhbuild update
./sugar-jhbuild build

After running build you may get a list of required packages that need to be installed from YAST. Most of them are available; the rest you'll need to search for or compile from source. Then run build again.

The first time I ran sugar, it seg-faulted. We traced the problem down to an issue loading the olpc theme. I am running KDE on suse, so there might be some misconfiguration of gnome there, I'll figure it out later, right now I am happy with the workaround even if the interface doesn't look as shakadelic.

The workaround is to comment out the following two lines in sugar/__init__.py

if settings.get_property('gtk-theme-name') != 'olpc':
      settings.set_string_property('gtk-theme-name', 'olpc', )