Sugar on Debian: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(38 intermediate revisions by 22 users not shown) | |||
Line 1: | Line 1: | ||
{{ |
{{jhbuild-nav}} |
||
== Page moved to Sugar Labs == |
|||
'''This page has been [http://wiki.sugarlabs.org/go/Community/Distributions/Debian moved] to the Sugar Labs wiki.''' |
|||
Please contribute instructions for getting [[Sugar]] to work with [http://debian.org/ Debian GNU/Linux]. |
|||
== See also == |
|||
------- |
|||
* [[Installing Debian as an upgrade]] |
|||
You pretty much need to use sugar-jhbuild. However, you can minimize the work it does without undue strain on your system (i.e., without resorting to use of experimental packages and the like). |
|||
== Get sugar-jhbuild == |
|||
aptitude install git-core |
|||
Get sugar-jhbuild through git as described on [[Sugar_with_sugar-jhbuild]] |
|||
== Run sugar-jhbuild == |
|||
cd sugar-jhbuild |
|||
./sugar-jhbuild update |
|||
./sugar-jhbuild build |
|||
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. If you want to save yourself some work, there are some packages that can be installed through apt rather than via build-base: |
|||
aptitude install darcs libdbus-1-dev libenchant-dev libfribidi-dev libgconf2-dev libgsf-1-dev libgstreamer-plugins-base0.10-dev libxslt1-dev libxul-dev python-avahi python-cairo-dev xserver-xephyr xulrunner |
|||
But we're still missing python2.5 and some python2.5 modules that need separate compilation. |
|||
------- |
|||
[[Category:Installing Sugar]] |
[[Category:Installing Sugar]] |
||
[[Category:Python]] |
Latest revision as of 18:52, 25 September 2010
Developer's Setup |
Fedora |
Ubuntu |
Debian |
Gentoo |
Slackware |
Wiki Category |
modify |
Page moved to Sugar Labs
This page has been moved to the Sugar Labs wiki.