All developed work is root off a some base release. Before any other command can be executed, the user needs to indentify in which base release to work and his SRT environment.
Because it is flexible and each distribution has opted for different features, setting up the environment is the most confusing part of using SRT. The user needs to work out of a test release. If he doesn't already have one, he needs to create one with the SRT "newrel" command. This only needs to be done once, and the user can work from the this area indefinitely. Additionally, the user needs to run srt_setup in each shell that his wishes to develop in, ie, each time he logs in or creates an xterm. There is a bit of a chicken and egg problem here in that some srt_setup switches require that a test release already have been created (e.g., -A), but you can't create the test release until srt_setup has been run. The solution is to execute srt_setup twice.
Note that the user can have more than one test release and switch between them, but this is not recommended for the novice SRT user. An additional note is that if you have if you have done an srt_setup -A and switch test releases, you need to run srt_setup again.
SRT is very loosely coupled with UPS. It has no requirements on UPS itself, but is modelled after it. Certain environment variables must be defined, e.g., ??? SRT_DIST in a global file and then srt_setup run. Code librarians have wrapped this distribution specific scripts. Again, check with your code librarian for your specific instructons.
cdfsoft/cdf2.cshrc
btev/setup.cshrc [<base-release>]
where the files d0local.login and cdf2.cshrc define the UPS databases for D0 and CDF in Run II: the appropriate file can either be sourced interactively or in the users .login file.
How does it know SRT_DIST??? The setup commands define the SoftRelTools enviromental variables SRT_DIST, SRT_BASE_RELEASE, and SRT_ARCH. SRT_DIST is the main directory, SRT_BASE_RELEASE is the release identifying name or number in the $SRT_DIST/releases directory, and SRT_ARCH specifies the UNIX operating system type and version number. <base-release> is an optional argument specifying the release, and if absent will default to the current release. Note that SRT_BASE_RELEASE is not a pathname. For example, the SRT_BASE_RELEASE release would be found at $SRT_DIST/releases/$SRT_BASE_RELEASE, so SRT_BASE_RELEASE could be a name like ``current'' or a number like ``1.0.4''. In addition, if using in a UPS environment, it defines a convenient environmental variable (<project>_DIR, which is CDFSOFT2_DIR, D0RUNII_DIR, etc.) which points at the area $SRT_DIST/releases/$SRT_BASE_RELEASE. Libraries and include files from packages will be taken from the <project>_DIR area, when linking and compiling, unless another area is specified by a test release (see section 3.4).