Sugar on Fedora Core 5

This tutorial is intended to be used by those of us who are interested in the project, but not to the degree with which we might gain access to the hardware :-)

I have made this relatively granular in detail, as that is what I would have liked to have seen--especially as a relative novice. My hope is that others might have an easier go of it!

Note: This is a work in progress. It is not complete, due to Python not being able to see several modules required by Sugar. If you have experience with Python environment configuration, please edit this page! I am open to any and all comments/suggestions, and would like to get this up and running as a tutorial for others.

Get and install mercurial

   
        su -
	rpm -i mercurial-0.9-1.fc5.i386.rpm (*see below)

Get Sugar from repository

        hg clone http://hg.fedoraproject.org/hg/olpc/applications/sugar--devel

Get dependencies ironed out

	
        yum install gnome-common

	yum install gtk2 gtk2-devel (Note: this is libgtk2.0 in Debian distros)

	yum install libstdc++ (which pulled multiple dependencies of its own!)
	
	yum install libstdc++.so.5 (even though libstdc++.so.6 existed!)

	yum install avahi

	yum install avahi-qt3

	yum install dbus

Create symbolic link for libstdc++

	ln -s /usr/local/lib/libstdc++.so.5 /usr/lib/libstdc++.so.5

Install xulrunner (gecko-embed depends on it)

	tar -xzf xulrunner-1.8.0.1.en-US.linux-i686.tar.gz 

	(they recommend untarring to /opt/xulrunner/1.8.0.1, I used /opt/xulrunner)

	/opt/xulrunner/xulrunner --register-global

Install gecko-embed from cvs

	cvs -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co gecko-embed

Build gecko-embed

	cd gecko-embed 
	./autogen.sh
	make 
	make install (as root or use sudo)

Get and Install avahi from avahi.org

	tar -xzf avahi-0.6.11.tar.gz
	./autogen.sh

Build Sugar

	cd sugar--devel
	./autogen.sh
	make

Run Sugar

	avahi-daemon -D (may already be running)
	
	./sugar/sugar

	Note: Sugar does not run, but throws ImportError: No module named avahi.
                     I believe this is due to PYTHONPATH or PATH not being set correctly?

NOTES

* Path will be dependent upon where you saved the RPMs to, i.e., if you saved to the desktop, your path might be /home/<username>/Desktop/<rpm package name>