web: Remove horizontal line at the top of the page.

[paraslash.git] / web / download.in.html

diff --git a/web/download.in.html b/web/download.in.html
index fcdc1fe19c2ba02bf01ccbeba660b0483a9d6620..393fce9352d65a48f751735b886f5f57473dbfe3 100644 (file)
--- a/web/download.in.html
+++ b/web/download.in.html
@@ -1,15 +1,73 @@
-<h3><a name="download">Download</a></h3>
-
-<p> Only <a href="versions/">source</a> is available,
-including the <a href="versions/paraslash-cvs.tar.bz2">
-nightly cvs snapshot</a> (which may or may not compile at
-any given time). All regular releases are
-<a href="PUBLIC_KEY">cryptographically signed</a>.
-Anonymous (read-only) cvs access is also
-available. Checkout a copy with </p>
-
-<p> cvs -d
-:pserver:anonymous@cvs.systemlinux.org:/var/lib/cvs
-login </p>
-<p>(empty passwd)</p>
-<p> cvs -d :pserver:anonymous@cvs.systemlinux.org:/var/lib/cvs co paraslash </p>
+<h1>Download</h1>
+<hr>
+
+Paraslash is only available as source code, no binary packages are
+provided at this point. There are several ways to download the source:
+
+<ul>
+       <li> <em> git</em>.
+
+               Clone the git repository by executing
+
+               <p> <pre> <kbd> git clone git://paraslash.systemlinux.org/git paraslash </kbd> </pre> </p>
+
+               <p> The repository contains the full history of the
+               project since 2006, all work in progress and the source
+               code for the web pages. Choosing this option allows to
+               check out any of the four integration branches maint,
+               master, next, pu (see the
+
+               <a href="manual.html#git_branches">git_branches</a>
+
+               section of the manual). All previous releases
+               correspond to tagged commits and may be checked out
+               as well. Since development takes place in separate
+               topic branches the master branch is expected to be
+               more stable than any of the released versions. </p>
+
+               <p> Compiling from git requires additional tools,
+               notably the autoconf package must be installed. </p>
+
+       </li>
+
+       <li> <em> regular releases</em>.
+
+               All released versions can be downloaded as compressed
+               tarballs from the
+
+               <a href="releases/">download directory</a>.
+
+               These tarballs are
+
+               <a href="PUBLIC_KEY">cryptographically signed</a>
+
+               and contain a pre-generated configure script. They
+               can be compiled and installed without autoconf.
+
+       </li>
+
+       <li> <em>master tarballs</em>.
+
+               Whenever significant changes are incorporated a
+
+               <a href="releases/paraslash-git.tar.bz2">tarball</a>
+
+               of the current master branch is created. All changes in
+               this tarball will be included in the next release. Like
+               for regular releases, a configure script is provided
+               for convenience.
+
+       </li>
+
+       <li> <em>gitweb snapshots</em>.
+
+               The
+
+                       <a href="/gitweb/gitweb.cgi?p=.git;a=summary">gitweb</a>
+
+               page contains a snapshot link for each revision. This
+               allows to get a specific revision without downloading
+               the full history.
+
+       </li>
+</ul>