<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: the
- preferred way is retrieving a tar file on the ftp server and the
+<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 will be available soon.
+ cvs. Cvsup may be available soon as an alternative.
<ul>
-<p><li> <em>From a tar file</em>. This is the preferred way. Tar files
+<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 ftp server
- <a href="ftp://alisoft.cern.ch/pub/offline">
- ftp://alisoft.cern.ch/pub/offline</a>. The tar files include the
+ 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><pre>
$ cd $ALICE
$ setenv CVSROOT :pserver:cvs@alisoft.cern.ch:/soft/cvsroot
-$ cvs login # (passwd "cvs")
-$ cvs co -r Release-3-03 -d pro AliRoot
+$ cvs co -r Release-3-XX -d pro AliRoot
</pre>
<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-03"). So, for a full update, including
+ (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>
<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>$ cvs 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>$ cvs 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>
git://git.uio.no / u / mrichter / AliRoot.git / blobdiff