next up previous contents
Next: Installation in non-enforced Up: Installation in enforced Previous: Where to get

How to install the HEPiX package in enforced mode

  Once you get the package uncompressed or you checked you could access it through the /afs/cern.ch cell, you can install the package on your system.

You can achieve it using make.pl command. For a formal descrition of this command consult Annex A.

su to root, go under hepix-3.0.2-rs_aix32/ directory and then you have different possibilities which are listed below. The default is to install the HEPiX shells login scripts in enforced mode and locally on the machine. So the collections etc, hepix, bin, man1 should be installed locally on the machine (refer to table 1).

- get the help:
> ./make.pl -h

- use the fake mode to check what the default would do:
> ./make.pl -n

- install the recommended default:
> ./make.pl

- install the recommended default in verbose mode:
> ./make.pl -v

- install some components, overwriting the previous version:
> ./make.pl -v -F 1 -C hepix:cern:etc:bin:man1:xdm

- install only the system part under /etc (this allows you not to put the scripts locally under /usr/local/lib/hepix but to make them accessible via NFS):
> ./make.pl -v -F 1 -C etc

- install the scripts in 'debug' mode:
> ./make.pl -d

- install the hepix and the xdm collections in enforced mode:
> ./make.pl -v -F 1 -C hepix:etc:xdm

- install the CERN customisation of the HEPiX scripts:
> ./make.pl -v -F 1 -C cern

Table 1 gives you all the collections and the flags which control their installation.

  
Table 1: The files and directories installed by make.pl vs specified collections

The procedure saves any vendor shell configuration file under /etc under a name with extension .std. The restore (-r flag) part resets the vendor shell configuration files under /etc.

The procedure make.pl has a force option -F nb a verbose option -v and an option to install the debug mode -d.

In addition an option -n will fake the installation.

You must be aware that this command will not try to overwrite an existing file from a previous version. Use the flag -F 1 to do so. Using the flag -F 2 will force the creation of the directories themselves and might delete completely your old versions. Warning, if for example you have a symbolic link

    /usr/local/lib/hepix --> /afs/cern.ch/asis/@sys/usr.local/lib/hepix
then this link will be removed and a local directoy will be created if you are using the -F 2 flag. So be aware of what you want to do!



next up previous contents
Next: Installation in non-enforced Up: Installation in enforced Previous: Where to get



Arnaud Taddei
Tue Dec 12 08:15:58 MET 1995