From ATLAS-TRIUMF

[edit] Using Multiple Athena Releases

NOTE: I am no longer trying to maintain a true multiple release setup; the number of headaches was increasing steadily. This is left here in case you want to try it on your desktop...

For a long time I was very confused by the instructions for using multiple Athena releases. So here is the me-specific literal-minded version:

Install your release. Suppose you installed 10.5.0, and put it in /data/AtlasReleaseArea, so you now have /data/AtlasReleaseArea/dist/10.5.0. Suppose, moreover, that you had already installed 10.4.0 in the same place, so you also have /data/AtlasReleaseArea/10.4.0. Now, if you do "source setup.sh" in /data/AtlasReleaseArea, you will find to your extreme annoyance that you have set all the paths for 10.4.0 as well as 10.5.0 and in many cases they are contradictory and nothing works. My original kludge was to edit out all the lines in /data/AtlasReleaseArea/setup.sh that referred to older releases. This gets to be a pain because the file gets recreated every time you run pacman, so you have to keep doing it.

So instead, you create another directory. Call it (for my example) /data/UseAtlasReleaseArea/10.5.0. Now, cd to this directory. Run pacman -get /data/AtlasReleaseArea:10.5.0/AtlasRelease-slc3_ia32-opt. It only took a few minutes for me, so I guess this is probably working correctly now. Then do source setup.sh in /data/UseAtlasReleaseArea/10.5.0 instead of in /data/AtlasReleaseArea. But all other steps (e.g. source dist/10.5.0/Control/AthenaRunTime/*/cmt/setup.sh) still get run from /data/AtlasReleaseArea.

So, for this example, the complete installation sequence from a fresh login terminal is:

• cd /data/pacman-3.13.1 (or latest version if different)
• source setup.sh
• cd /data/AtlasReleaseArea (or whatever you call your installation area)
• pacman -get http://atlas.web.cern.ch/Atlas/GROUPS/SOFTWARE/OO/pacman/slc3/cache:10.5.0/AtlasRelease-slc3_ia32-opt
• (this is where you go for lunch)
• cd /data/UseAtlasReleaseArea
• mkdir 10.5.0
• cd 10.5.0
• pacman -get /data/AtlasReleaseArea:10.5.0/AtlasRelease-slc3_ia32-opt
• source setup.sh
• cd /data/AtlasReleaseArea/dist/10.5.0/Control/AthenaRunTime/*/cmt
• source setup.sh
• (SealPluginRefresh) in principle not needed since 10.0.2, confirmed not needed since 10.5.0
• (cmt build library_links) in principle not needed since 10.0.2, confirmed not needed for 10.5.0, but I did need it again to run RecExCommon under 11.0.0...
• and then use a Multiple Release Setup Script for future use of this release

(Note: when I switched from pacman 3.13 to 3.14 I was totally unable to install 11.0.0 in the directory I had been using for 10.4.1 and 10.5.0. The installation failed with "Error in Pacman. Complain to Pacman Headquarters http://physics.bu.edu/pacman/." I therefore had to put 11.0.0 in a new /data/AtlasReleaseArea2. But I was then able to do all the following steps as usual, updating my ATLAS_RELEASE_PATH variable to point to the new directory, and adding some lines to my Multiple Release Setup Script to reset it to the old value if I used one of the old releases. These lines are not in the example because this is a weird situation that should not happen.)

--Isabel 12:09, 13 Sep 2005 (PDT) --Isabel 15:44, 27 Oct 2005 (PDT)