How do I build/upgrade an ACS installation to a new CVS tag from sources?

See also: FAQMultipleACSInstalls and FAQACSCvsGet

Since ACS 2.0.1, we use CVS as the revision control system and not any more CMM. ACS releases and patches are identified by CVS tags that are published in the ACS Web Page.

You can download the tar ball with a new release/patch directly from the web page or you can download it from CVS with the following command:

> cvs export -r TagName ACS

This creates a directory structure with root in the ACS directory. Once you have the ACS directory structure you can upgrade an ACS installation with the following steps:

• Login as the same user that did the original installation. For example almamgr
• Make sure that you do not have any INTROOT. The user that installs ACS should never have INTROOT defined. It is also strongly advisable to delete all INTROOT areas in case of an ACS upgrade.

> echo $INTROOT

    if defined:
     > rm -rf $INTROOT
     > unset INTROOT

• The installation procedure makes automatically a backup copy of a previous installation.
  If you want to save space and not keep a backup copy, you can delete the current installation now:

     > rm -rf $ACSROOT

• You can also delete the backup copy when the installation will be completed.
• Build the new ACS

     > make build

• It is advisable to check if the template for environment setting in $ACSROOT/config/.acs/.bash_profile.acs has changed and in that case you should upgrade your copy in .acs or your own environment setting procedures.
• If you are going to use the ALMA Archive distribution you should first check the proper version out from CVS and build it.

That should be it!