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