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
12 <p> <pre> <kbd> git clone git://paraslash.systemlinux.org/git paraslash </kbd> </pre> </p>
14 <p> The repository contains the full history of the
15 project since 2006, all work in progress and the source
16 code for the web pages. Choosing this option allows to
17 check out any of the four integration branches maint,
18 master, next, pu (see the
20 <a href="manual.html#git_branches">git_branches</a>
22 section of the manual). All previous releases
23 correspond to tagged commits and may be checked out
24 as well. Since development takes place in separate
25 topic branches the master branch is expected to be
26 more stable than any of the released versions. </p>
28 <p> Compiling from git requires additional tools,
29 notably the autoconf package must be installed. </p>
33 <li> <em> regular releases</em>.
35 All released versions can be downloaded as compressed
38 <a href="releases/">download directory</a>.
42 <a href="PUBLIC_KEY">cryptographically signed</a>
44 and contain a pre-generated configure script. They
45 can be compiled and installed without autoconf.
49 <li> <em>master tarballs</em>.
51 Whenever significant changes are incorporated a
53 <a href="releases/paraslash-git.tar.bz2">tarball</a>
55 of the current master branch is created. All changes in
56 this tarball will be included in the next release. Like
57 for regular releases, a configure script is provided
62 <li> <em>gitweb snapshots</em>.
66 <a href="/gitweb/gitweb.cgi?p=.git;a=summary">gitweb</a>
68 page contains a snapshot link for each revision. This
69 allows to get a specific revision without downloading