DevelopmentTeam/Jhbuild/Debian
From Sugar Labs
| Google Translations-Español-Български-中文(中国大陆)-中文(台灣)-Hrvatski-Česky-Dansk-Nederlands-Suomi-Français-Deutsch-Ελληνικά-हिन्दी-Italiano-日本語-한국어-Norsk (bokmål)-Polski-Português-Română-Русский-Svenska |
This Page is being considered for moving from OLPC
Information on moving content between wikis can be found at Transwiki.
Please use the discussion page to make comments about
how this move affects you and see other's comments.
| Developer's Setup |
| Fedora |
| Ubuntu |
| Debian |
| Gentoo |
| Slackware |
| Wiki Category |
| modify |
Contents |
Debian repository for sugar-jhbuild
There is a repository for weekly builds of sugar-jhbuild.
You can get it by adding the following line to your /etc/apt/sources.list
deb http://download.sugarlabs.org/sugar/liveimages/debian-jhbuild/apt/ sid main
Then type:
apt-get update apt-get install sugar-jhbuild
Now you can try sugar in a seprate window:
sugar-jhbuild-emulator
You will also have login option in gdm/kdm/xdm.
Easy Steps for building sugar-jhbuild
These 3 easy steps will get sugar running for you on Debian.
1 . Get sugar-jhbuild
Get sugar-jhbuild through git as described in jhbuild.
Make sure you have git:
apt-get install git-core
Then as user:
git-clone git://dev.laptop.org/sugar-jhbuild
2 . Get lsb-release and icon-slicer
You will need this so that jhbuild will identify this is a debian system.
apt-get install lsb-release
You will also need icon-slicer, which isn't in the Debian repository. However you can get it like this:
wget http://www.mithril-linux.org/~henrich/debian/package/icon-slicer/icon-slicer_0.3-1_i386.deb dpkg -i icon-slicer_0.3-1_i386.deb
3. Run sugar-jhbuild
cd sugar-jhbuild ./sugar-jhbuild update ./sugar-jhbuild build
When you run ./sugar-jhbuild build you will get the list of packages you are missing to build sugar.
So then run:
apt-get install [list of missing packages]
And then again:
./sugar-jhbuild build
After a long time the compiling will finish and you can type:
./sugar-jhbuild run
Getting Telepathy working
To get telepathy working you need to enebale the avahi server that is not always on by default.
/etc/init.d/avahi-daemon start
Then you can browse for other XOs (real or simulated)
avahi-browse -t _presence._tcp
old list of packages
This section is obsolete because now there is a configuration file for debian. Just follow the 3 steps above.
For build-base, you should need:
apt-get install libtool libsqlite3-dev libnspr4-dev docbook-xsl intltool \ librsvg2-dev gtk-doc-tools libglade2-dev icon-naming-utils cdbs devscripts \ quilt patchutils python-dev python-central debhelper dh-buildinfo \ libglib2.0-dev python-gtk2-dev gettext shared-mime-info python-empy libgconf2-dev \ libgsf-1-dev libenchant-dev libwv-dev libboost-dev libgnomevfs2-dev
Now, this is ALL you need if you want to spend many hours compiling many packages:
Errors during update
If update fails with:
ImportError: No Module name ctypes
Try running
aptitude install python-ctypes
Plenty of dependencies are likely to fail.
Errors during build
You will also need icon-slicer (for stage 22) , which isn't in the debian repository. However you can get it like this:
wget http://www.mithril-linux.org/~henrich/debian/package/icon-slicer/icon-slicer_0.3-1_i386.deb dpkg -i icon-slicer_0.3-1_i386.deb
The Dependencies
You have two ways to get the dependencies: Build-base and building/installing packages manually from sid archives.
Alternative 1: Build Base
This is easy, but it takes a long time and builds custom versions of all the dependencies (rather than getting them through apt).
./sugar-jhbuild build-base
This takes a long time, but will work. After that, do 'build' and 'run'.
Alternative 2: Install dependency libraries directly from Debian Sid
- Debian Sugar (contains notes both on official packaging and on build-dependencies for manual builds)
Related bugs
- package status for OLPC-related packages, including links to bugs.
Debian-OLPC
- Now there is an debian-olpc project alioth debian-olpc
- You can join the mail list
External links
See also
Problems and Solutions
- It seems plausible that while run dependency check, python-cairo and gtk2.0 have problems while instaling dependencies, (dev libraries) try installing first the gtk2.0 libraries, that should erase the dependence on python-cairo.
