<HEAD>
<TITLE>Installation</TITLE>
-<link rev="made" href="mailto:Federico.Carminati@cern.ch">
+<link rev="made" href="mailto:webmaster@alisoft.cern.ch">
<link rel="stylesheet" href="http://www.w3.org/StyleSheets/Core/Swiss" type="text/css">
<STYLE type="text/css">
the installation on other systems and we will be happy to consider
modifications and corrections necessary to make the installation possible.
-<p> The disk space required for a full installation of AliRoot is 200MB for
-the system itself and 60MB for the ROOT system.
+<p> The disk space required for a full installation of AliRoot is 360MB for
+the system itself and 120MB for the ROOT system.
<h3>gmake</h3>
<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. This code is available under 3 main
+ versions (old, pro and new). Check <a href="../releases.html"> the
+ Releases page </a> to select the appropriate version and get
+ the corresponding CVS Tag.
+ There are two ways to retrieve the code: the
+ preferred way consists in retrieving a tar file on the ftp server and the
+ slow and network consuming way is checking out the whole cvs tree using
+ cvs. Cvsup may be available soon as an alternative.
+
<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>. Tar files
+ for the different releases including an up-to-date file remade
+ every night are available on the
+ <a href="http://AliSoft.cern.ch/offline/download/offline/">
+ Web server</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> ChangeCVSRoot asmith </pre>
+
+<p><li> <em>From cvs remote cvs server</em>. The setup for the access
+ to the remote cvs server is described in the
+ <A HREF="/offline/development.html#Code">Code Development section</A>.
+ The code can be downloaded via the following commands:
+
<p><pre>
$ cd $ALICE
-$ cvsa co -r Release-3-02 -d pro AliRoot
+$ setenv CVSROOT :pserver:cvs@alisoft.cern.ch:/soft/cvsroot
+$ cvs co -r Release-3-XX -d pro AliRoot
</pre>
-<p>Where the meaning of <kbd>cvsa</kbd> is explained in the
-<a href="../development.html">code development</a> section.
+<p><li> <em> Update </em> In both cases running a cvs update command
+ will update the latest changes to the code in the selected branch
+ (here branch "Release-3-XX"). So, for a full update, including
+ the automatic creation a new subdirectories, the commands are:
+<p><pre>
+$ cd $ALICE/pro
+$ setenv CVSROOT :pserver:cvs@alisoft.cern.ch:/soft/cvsroot
+$ cvs update -d
+</pre>
</ul>
<p>Therefore in order to develop one or more packages locally
(let's say the TPC) and make modifications, the following steps should be
-performed. We suppose here that the remote cvs server has been setup correctly
-as explained in the <a href="../development.html">code development</a> section.
+performed. The remote cvs server use and setup is explained in the <a
+href="../development.html">code development</a> section.
<p><table id="wide" cellspacing=10%>
<tr align=center>
<td>remove link to ALIROOT subdirectory, may be this is not really necessary
on all systems, but we do it just to be on the safe side
<tr align=left>
- <th>$ cvsa co -r Release-3-02 TPC
+ <th>$ cvs co -r Release-3-XX TPC
<td>get from the cvs server the release version of the TPC files to be
modified
<tr align=left>
- <th>$ cvsa co -r Release-3-02 ALIROOT
+ <th>$ cvs co -r Release-3-XX ALIROOT
<td>get from the server the release version of the ALIROOT files to recreate
the executable
<tr align=left>
<hr>
<address>
<script language="JavaScript">
- document.write("Last modified "+ document.lastModified)
+ document.write("Last modified "+ document.lastModified +" . ")
// end of script -->
</script>
-by <a href="mailto:Federico.Carminati@cern.ch">Federico Carminati</a>
+Please report problems to
+<a href="mailto:webmaster@alisoft.cern.ch"> webmaster@alisoft.cern.ch</a>
</address>
</BODY>
</HTML>
git://git.uio.no / u / mrichter / AliRoot.git / blobdiff