4 <p> Paraslash is only available as source code, no binary packages
5 are provided at this point. There are several ways to download the
11 Clone the git repository by executing
14 git clone git://git.tuebingen.mpg.de/paraslash.git
17 <p> The repository contains the full history of the
18 project since 2006, all work in progress and the source
19 code for the web pages. Choosing this option allows the
20 checkout of any of the four integration branches maint,
21 master, next, pu (see the
23 <a href="manual.html#Git-branches">Git branches</a>
25 section of the manual). All previous releases
26 correspond to tagged commits and may be checked out
27 as well. Since development takes place in separate
28 topic branches the master branch is expected to be
29 more stable than any of the released versions. </p>
31 <p> Compiling from git requires additional tools,
32 notably the autoconf package must be installed. </p>
36 <li> <em> regular releases</em>.
38 All released versions can be downloaded as compressed
41 <a href="releases/">download directory</a>.
45 <a href="PUBLIC_KEY">cryptographically signed</a>
47 and contain a pre-generated configure script. They
48 can be compiled and installed without autoconf.
52 <li> <em>master tarballs</em>.
54 Whenever significant changes are incorporated a
56 <a href="releases/paraslash-git.tar.xz">tarball</a>
58 of the current master branch is created. All changes in
59 this tarball will be included in the next release. Like
60 for regular releases, a configure script is provided
65 <li> <em>gitweb snapshots</em>.
69 <a href="http://git.tuebingen.mpg.de/paraslash.git">gitweb</a>
71 page contains a snapshot link for each revision. This
72 allows getting a specific revision without downloading