The UPS setup of a particular release sets the user's path, manpath, etc., in such a way that binaries are directly accessible, include files can be available through an environment variable pointing to the release ``include/'' tree, and the libraries can be used by a reference to the library tree environment variable via the ``-L'' compiler option.
The directory structure assumes that most users will make use of a complete release, rather than mixing-and-matching packages across releases. If, however, a user would like to work with release ``A'' of a product but use version ``B'' of a package ``pkgC'', s/he should use the SRT ``newrel'' command to recreate the release structure in his/her own working directory. To this command the user has to specify version ``B'' of package ``pkgC''. Version ``B'' of pkgC needs to be built in this new test release context. The user can then link his/her own executable against this new test release.
Those users who want to write their own scripts and makefiles just need to know a few things. As discussed in section 3.1, the UPS setup defines the environmental variables SRT_DIST and SRT_CURRENT. The environmental variable SRT_ARCH is also defined to indicate the flavor of operating system, as discussed in appendix B.3.4. In principal, these are the only environment variables you need to use the software release structure. Although we strongly recommend the use of our setups and makefiles, the user is free to suitably define these variables to point at the right areas, and then write their own scripts and makefiles. The user needs to know that compilation with package include files is accomplished using the compilation option -I$SRT_DIST/releases/$SRT_CURRENT/include, and linking with package libraries is accomplished using the link option -L$SRT_DIST/releases/$SRT_CURRENT/lib/$SRT_ARCH. Users who prefer to do it themselves should be able to use this information to write their own sripts and makefiles. However, we recommend that the provided scripts and makefiles be used.