Next: , Previous: , Up: User's manual   [Contents][Index]

2.2 Getting the game

2.2.1 Download source

Liquid War 6 can be found on:

Downloading the latest file from this place, and compile it yourself on your computer with a classical ./configure && make && make install is the recommended way to install Liquid War 6.

2.2.2 Download binaries

Some binary packages might be available. Your mileage may vary.

GNU/Linux based systems are supported, through Debian .deb and Red Hat RPM packages. There is also a Microsoft Windows installer.

However these binaries are not necessarly available for every single version of the game.

2.2.3 GIT repository

Latest work in progress versions can be obtained with GIT. Here’s the typicall command which will fetch the latest version:

git clone git://

If you are behing a firewall and can’t use the native GIT protocol, you can rely on the (slower) http protocol:

git clone

You can browse the code online, consult log summary, and in a general manner “follow” the project on and

Beware, git does not contain all the files included in the official source tarball. For instance, the ./configure script is not present. You need to run :

make install

The autoreconf call is really mandatory the first time, autoconf is not enough. You will also need all the prerequisites needed to build the docs, generally speaking, getting the source from git requires more tools to build the package than picking a ready-to-use tarball.

2.2.4 Daily snapshots

Alternatively, you can download daily snapshots on These files used to be built every day, now they are generated by Jenkins whenever there’s a source change (commit). A simple make is done before generating source tarballs however a make distcheck is performed before generating binaries, therefore sometimes you can have the source but no associated tarballs.

Beware of revision numbers, snapshots can make you believe version X.Y is out when it’s only a release candidate at best, and most of the time just a work-in-progress.

Still, if you want bleeding edge versions, this is the way to go.

Documentation is automatically updated as well, and available on

2.2.5 Check integrity

Most binary packages (at least .deb and RPM GNU/Linux binaries) should be signed using GnuPG. The following keys are used when generating upstream/vendor packages:

Next: , Previous: , Up: User's manual   [Contents][Index]