Development Team/Jhbuild: Difference between revisions
Sascha silbe (talk | contribs) →Customize: ~/.sugar.jhbuildrc doesn't get read any more |
Sascha silbe (talk | contribs) →Prerequisites: no Mac support, update svn repo remark |
||
| Line 33: | Line 33: | ||
: The sugar-jhbuild command is a Python script, so you need the Python interpreter. | : The sugar-jhbuild command is a Python script, so you need the Python interpreter. | ||
; git | ; git | ||
: To get the source code of sugar-jhbuild itself and many other Sugar packages you need the < | : To get the source code of sugar-jhbuild itself and many other Sugar packages you need the <code>git</code> command-line tool from the distributed version control system of the same name. In many distributions the minimal package you need to install is "git-core". | ||
; svn | ; svn | ||
: A few packages (as of | : A few packages (as of January 2010, only squeak and part of etoys) do not use git, and you need the <code>svn</code> command-line tool from the Subversion version control system to get their source code. | ||
These should be enough to run sugar-jhbuild on a typical Linux | These should be enough to run sugar-jhbuild itself on a typical Linux installation. Running <code>sugar-jhbuild depscheck</code> (see below) will probably list dozens of additional required packages. | ||
==Check out sugar-jhbuild== | ==Check out sugar-jhbuild== | ||