Information
We are currently investigating an issue with the editor of some pages. Please save your work and avoid to create new pages until this banner is gone.
Is it mandatory that I install ACS in the /alma directory?
Several people have wondered whether ACS requires installation in /alma or whether another directory name can be used. For example, you may have noticed (in the .acs/.bash_profile.acs file) an environment variable named ALMASW_ROOTDIR and wondered whether it could be as simple as changing the installation directory (to something other than /alma) and updating the .bash_profile.acs to define ALMASW_ROOTDIR to point to the new directory (rather than to /alma). Unfortunately, though this seems logical, it won't work.
Simply changing the installation location of ACS and updating the ALMASW_ROOTDIR environment variable will NOT work, because Python has some hardcoded absolute paths that are generated at build time and therefore it is not "relocatable". But there are a number of things you can do instead, depending on what your goal/problem is:
A. If you really need to install ACS somewhere else, for example because your sysadmin will not give you access to the /alma directory, you can rebuild the tools in the location where you will be installing ACS; by rebuilding there, the python paths which are generated at build time will be correct for your installation:
B. If you can use /alma but you want to put an ACS-5.0 complete tree somewhere else, you can get away with symbolic links; as long as Python can find its directory in /alma/ACS-5.0 it will work.
C. Normally you should not need to have multiple installations of the tools, but only of ACSSW, for the different patches. In that case you can have multiple ACSSW-X.Y.Z directories inside ACS-5.0 and change just the ACSROOT variable. This saves a LOT of space.
As per ACS 10.0 this problem is fixed, the hardcoded path in omniORB was removed, the path required by omniORB is generated dynamically in runtime according the variables set in your environment.