Using base and test releases on novatest01

Setting up the SRT environment, including a base release:

You just need to source /nova/novadaq/setup/setup_novadaq_nt1.[c]sh, as appropriate for your shell. (Good taste dictates that csh is never appropriate.)

You might want to make this a function in your .bash_profile, e.g.,

function setup_novadaq

        source /nova/novadaq/setup/ "$@" 

By source'ing with no arguments, you get the default base release, which is currently development.

You can choose another base release with the -r argument. E.g.,

source /nova/novadaq/setup/ -r name_of_an_existing_release

Source'ing this script will also do the UPS setups of all external packages known to the base release.

Making a test release:

A test release is your personal environment for creating new code and/or modifying existing code. You can create as many test releases as you need, but they persist until you delete them.

To make your own test release, to modify and/or create code:

> cd some_directory_you_own
> newrel -t base_release_name test_release_name

The -t argument means "test" release. Rather than check out all packages and rebuild them, you will use all but the ones you want to modify from the base release base_release_name, e.g., development. test_release_name is the name of the subdirectory where your test release will exist.

Using your test release

Once you have created the test release, you need to set it up for any new shell session with

> cd [test_release]
> srt_setup -a

-a means "autolocal", which tells SRT that the test release to use is in the current directory.

You can checkout an existing package to modify with

> addpkg [-h] package_name

where -h is for the HEAD version. If you're using anything other than development as your base release, you probably want to leave that off, so that you'll pick up the tagged CVS version of that package associated with that frozen release.


> addpkg -h NovaDAQTemplate

You can make the package with

> gmake NovaDAQTemplate.all

If it's been a while since you checked out the package, it's probably a good idea to do a "cvs diff -r tag_name", or "cvs update".
You can modify the source code and remake it, and check it back in when all changes are tested and agreed to, with "cvs commit".

To create a new package, learn about newpkg here.