ROXTerm
Author: Adrian Sampson
Description: ROXTerm, a full-featured VTE terminal emulator

- На главную
- Новости
- Установка
- Руководство пользователя
- Форум

# Installation

## Download :

Visit the SourceForge project page to download release files or use other Sourceforge tools. If you want to get developmental versions ahead of releases, use git. For versions prior to 1.19.0 use svn (subversion). The actual command you will probably want to use to check out a snapshot is:

git clone git://git.code.sf.net/p/roxterm/code roxterm

## Requirements :

You need the libraries for GTK+2 which is pretty much standard on all free Unix derivatives these days, and/or GTK+3. It needs at least version 2.16 of glib and GTK+ 2.18. You will also need vte/libvte (at least version 0.20), a Gnome component; most distros package separate versions for GTK+2 and GTK+3. D-BUS is also required (see below).

To compile ROXTerm you will need the header files for the above libraries. In packaging systems they usually come in packages whose names end in "-dev" or "-devel".

ROXTerm uses a new, bespoke build system called maitch. This requires python and the python 'lockfile' module.

### D-Bus

D-Bus is a messaging system which ROXTerm uses to connect terminals with its configure tool. ROXTerm uses the "session" bus, which should be started along with your desktop environment. Current versions of ROX, GNOME and KDE session managers all launch D-Bus. If you use some other session/desktop/window manager which doesn't launch D-Bus you can start it by inserting something like this near the start of your .xinitrc or .xsession:

if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then eval `dbus-launch --sh-syntax --exit-with-session` export DBUS_SESSION_BUS_ADDRESS fi

The reason for using a bespoke configuration messaging system over D-Bus instead of gconf is because gconf doesn't provide a way to map an arbitrary number of profiles onto configuration filenames.

## Installing :

To install ROXTerm for ROX all you need to do is unpack the tarball in your Apps directory and run it from there, but you will probably want to rename the folder to ROXTerm. For other systems ROXTerm may be installed in a similar way to an autoconf-based source package, but using maitch's analogues:

python ./mscript.py configure python ./mscript.py build python ./mscript.py install

Various options are available, run

python ./mscript.py help

for details.

Autoconf builds are no longer supported.

### Debian & Ubuntu

Up-to-date official Debian packages are now available. See http://packages.debian.org/roxterm.

Ubuntu also has official roxterm packages, but due to Ubuntu's release cycle these may lag behind the latest upstream releases. Therefore I have set up a PPA to provide the most recent releases of ROXTerm for Ubuntu's current release when appropriate.

For those that want to build their own debian packages, the debian packaging files are no longer included in release tarballs, but they are included in git's master branch. See above for details of how to fetch roxterm from git.

If you want to build a particular version:

`git checkout` version

For older distros which do not include packages of GTK3 etc:

`git fetch origin lucid:lucid
git checkout lucid`

You can use `sudo apt-get build-dep` at this point, but depending on the version already in your distro the set of packages may be out-of-date, so be prepared for dependency errors later and install the necessary packages at that point. You should install imagemagick and librsvg2-bin at this point, but these are bugged in Ubuntu Lucid (and earlier?), so before building you will have to copy these files from `Help/lib` in a tarball: `roxterm_logo.png favicon.ico logo_text.png`.

If not using a release snapshot it's a good idead to use `dch` to ensure the newest version number in `debian/changelog` has an appropriate version number eg what `./mscript.py configure` generates in the file `version`, based on the output of `git describe`. Now you can build the packages eg with `debuild -b -uc -us`. Note the `-b`:- only binary packages can be built in the absence of an orig tarball.