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.
The preparation of the environment is usually a very easy task.
Before the installation, you would load up the environment using:
source <repo-path>/ACS/LGPL/acsBUILD/config/.acs/.bash_profile.acs
After the version is installed, you would have to load the environment from the installed ACS version:
source /alma/ACS-<version>/ACSSW/config/.acs/.bash_profile.acs
This needs to be done in every console that is going to be used for working with ACS.
There are different options for configuring the ACS environment. This is usually done using the Linux facilities for user or system environment configuration (aliases, .bash_profile, .bashrc, /etc/profile*, etc.).
Here are some examples to configure the environment at user level:
If the environment is going to be used constantly for ACS development (testing or even production), you could simply add this line to the user's ~/.bash_profile or ~/.bashrc file, so it will be available each time a console is opened.
Another alternative is to prepare aliases that load different ACS releases. For instance:
alias acs='source ~/.profs/.acs'
if [ "$1" == "" ]; then #Default ACS version source /alma/ACS-2020FEB/ACSSW/config/.acs/.bash_profile.acs -r else if [ -e $WORK/branches/$1 ]; then source /alma/ACS-$1/ACSSW/config/.acs/.bash_profile.acs -r else echo "Branch $1 not available. List of available branches is:" for i in $(ls -d /alma/ACS-*); do echo -e "\t$i" done fi fi
#Load default ACS environment acs #Load specific ACS version acs 2020APR