The setup of UPS packages is done automatically when the SRT base release is set up. The file $SRT_BASE_RELEASE/setup/ups_products- release_name ($SRT_BASE_RELEASE/setup/ups_products- release_name-LinuxPPC for the DCMs) and contains arguments for each ups setup command that is needed. E.g., a fragment of the ups_products-development file as of October 13, 2009 gives

jca      v2_3_2
root     v5_24_00  -q GCC_4_1_2
smc      v5_0_0

etc., which invokes
setup jca  v2_3_2
setup root v5_24_00  -q GCC_4_1_2
setup smc  v5_0_0


The ups setup script accomplishes this with

> source SRT_BASE_RELEASE/setup/ups_products- release_name

If you need to try other products and/or versions for your base release, you'll probably want to create your own versions file, and source as shown above, after setting up your test release for the session.

When a new release is declared, a corresponding version of this file will need to be created and check into onlsetup.

NOTE: SRT expects a directory named setup. Since there already is such a directory in our repository for the offline, the actual cvs module name is onlsetup. Our SRT bootstrapping should ensure that we effectively do a "cvs checkout -d setup onlsetup", but if you need to do this yourself at any point, you'll need to be aware of the distinction. As of 10/12/09, there is a NOvA-specific version of addpkg in SRT_NOVADAQ which should do the same, but it only works with the head version:

> addpkg -h -M onlsetup setup