Development Snapshots

Here are various ways to install the development version of Spot. If you are want a short summary of watch changed since the previous release, check the NEWS file. Beware that this file is not always completely up-to-date: we usually make final editing pass on the file right before making a release.

Debian packages

We build Debian packages nightly, for amd64 and i386. (This happens between 3am and 5am if the next branch has been changed in the repository.)

The packages are built for Debian stable (a.k.a. Jessie) and Debian unstable (a.k.a. Sid). The stable packages are built from the stable branch (this branch basically follows master but might include additional fixes), and the unstable packages follow the next branch.

Since this page is concerned with development snapshots, here is how to get the unstable packages:

echo 'deb http://www.lrde.epita.fr/repo/debian/ unstable/' >> /etc/apt/sources.list
apt-get update
apt-get install spot libspot-dev spot-doc python3-spot # Or a subset of those

The package spot contains the libraries and binaries. libspot-dev contains the header files if you plan to use Spot in a C++11 program (please keep in mind that the C++ API will undergo a lot of changes before we release version 2.0). spot-doc contains some html and pdf documentation. Finally python3-spot contains some Python bindings (this package also installs some ipython notebooks that you can use as examples).

From a tarball

Our build farm generate tarballs from each successful build. Here is a link to the last successful one (you want the file that is named spot-*.tar.gz).

Be sure to read the included README file for building instructions.

From Git

The master branch of the git repository currently contains the code for latest release, possibly with some additional bug fixes. The stable branch is like master, except it tracks the version for which the Debian stable packages are made (and also the version used by the web site). stable could be a bit behind master if the patches pending on master are not important enough to rebuild the packages and web site.

The next branch contains the (working) code that should be part of the next release. When we speak of the development version, we refer to the next branch.

To clone the git repository, use

git clone https://gitlab.lrde.epita.fr/spot/spot.git

This should put you in the next branch by default. Then continue building as specified in the HACKING file.