From 78fbaa94cc86fea7e3dfc2a46bc05c7c49bc118f Mon Sep 17 00:00:00 2001
From: vcolin <vcolin@f7af4fe6-9843-0410-8265-dc069ae4e863>
Date: Mon, 29 May 2000 15:31:40 +0000
Subject: [PATCH] update of the cvs/ftp retrieve informations.

---
 html/installation.html | 61 ++++++++++++++++++------------------------
 1 file changed, 26 insertions(+), 35 deletions(-)

diff --git a/html/installation.html b/html/installation.html
index cacc2420dce..66fd1addc17 100644
--- a/html/installation.html
+++ b/html/installation.html
@@ -140,42 +140,33 @@ necessary variables correctly.
 <p>At this point you should logout, login again and check that the symbols
 are set correctly.
 
-<p><li> Retrieve the AliRoot code. There are two ways to do this:
-
+<p><li> Retrieve the AliRoot code. There are two ways to do this: the
+    preferred way is retrieving a tar file on the ftp server and the
+    slow and network consuming way is checking out the whole cvs tree.
+    
 <ul> 
-<p><li> <em>From a tar file</em>. This is the preferred way for those who
-do not have an internet connection to the <em>cvs</em> server from the
-machine where the code has to be installed. The <a
-href="ftp://pcepaip01.cern.ch/pub">files</a> containing the latest release
-should be brought on the target machine. Three files are offered:
-
-<p><table align=center borders=no>
-<tr><th align=left>File<th align=left>Content</tr>
-<tr><td align=center colspan=2><em>Either</em></tr>
-<tr><td>AliOffline<i>MM.mm-pp</i>.tar.gz
-<td>Code and the data files of ALICE Off-line</tr>
-<tr><td align=center colspan=2><em>Or</em></tr>
-<tr><td>AliLibs<i>MM.mm-pp</i>.tar.gz
-<td>Code and the data files of the auxiliary libraries</tr>
-<tr><td>AliRoot<i>MM.mm-pp</i>.tar.gz
-<td>All the code and the data files of the AliRoot system</tr>
-</table>
-
-<p> <i>MM.mm-pp</i> is the number of the latest <i>M</i>ajor and
-<i>m</i>inor version and the <i>p</i>atch number. The file(s) have to be
-unpacked into the $ALICE directory via the command:
-
-<p><pre>$ gtar xvfz Ali[...].tar.gz</pre>
-
-
-<p><li> <em>From cvs remote cvs server</em>. This method has the advantage
-that new patches can be incrementally retrieved and installed via internet.
-At the moment the problem is that the version of cvs currently installed at
-CERN (1.09) does not support well binary files. Therefore some data files
-will be missing with this download mechanism, and these will have to be
-fetched <em>by hand</em>. The setup of the access to the remote cvs server
-is described in the Code Development section. The
-code is dowloaded via the command:
+<p><li> <em>From a tar file</em>. This is the preferred way. Tar files
+    for the different releases including an up-to-date file remade
+    every night are available on the ftp server
+    <a href="ftp://alisoft.cern.ch/pub/offline">
+    ftp://alisoft.cern.ch/pub/offline</a>. The tar files include the
+    "CVS" subdirectories for the anonymous cvs user (login "cvs"). So after
+    getting the full tar file, it is possible to incrementally update
+    the code using cvs.
+
+    <p> The tar file(s) can to be unpacked into the $ALICE directory
+    via the command: 
+    
+    <p><pre>$ gtar xvfz V3.XX.tar.gz</pre>
+    
+    <p> A script <a href="ftp://alisoft.cern.ch/pub/misc/">changeCVSRoot</a>
+    is available to convert a CVS tree under user "cvs" to another
+    user. For example, <pre> ChangeRoot tpc </pre>
+    
+
+<p><li> <em>From cvs remote cvs server</em>.  The setup of the access
+    to the remote cvs server is described in the Code Development
+    section. The code is dowloaded via the command:
 
 <p><pre>
 $ cd $ALICE
-- 
2.43.0