Sugar on Debian

From OLPC
Revision as of 13:39, 16 December 2008 by 198.83.124.250 (talk) (FIELD_OTHER)
Jump to: navigation, search

This Page is being considered for moving to Sugar Labs
Information on moving content between wikis can be found at OLPC:Transwiki#SugarLabs.
Please use the discussion page to make comments about
how this move affects you and see other's comments.

http://wiki.sugarlabs.org/go/Community/Distributions/Debian

Developer's Setup
 Fedora
 Ubuntu
 Debian
 Gentoo
 Slackware
Wiki Category
modify 

Please contribute instructions for getting Sugar to work with Debian GNU/Linux.


Installing sugar on Debian Unstable

Simplest is to use officially packaged Sugar packages:

aptitude install sugar

This method now works in Debian Testing as of May 22, 2008 (IAEP: Core Sugar framework now in Debian Testing!)

The rest of this page is about ways to build Sugar software yourself on a Debian system...

Get sugar-jhbuild

aptitude install git-core

Get sugar-jhbuild through git as described in Sugar with sugar-jhbuild.

Run sugar-jhbuild

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

If update fails with:

ImportError: No Module name ctypes

Try running

aptitude install python-ctypes

Plenty of dependencies are likely to fail.

For build-base, you should need:

aptitude install libtool libsqlite3-dev libnspr4-dev docbook-xsl intltool

Now, this is ALL you need if you want to spend many hours compiling many packages:

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)

FIELD_MESSAGE_ricracle

Debian-OLPC

External links

See also

Problems and Solutions

  • It seems plausible that while run dependency check, python-cairo and gtk2.0 have problems while installing dependencies, (dev libraries) try installing first the gtk2.0 libraries, that should erase the dependence on python-cairo.