mst_envs - configure MST environment
mst_envs [options]
output commands compatible with the specified shell
Only output the specified environment variable. This option may be repeated.
only output the environment variables
only output the path
add MST executables to the front of the user's path (default behavior)
add MST executables to the end of the user's path
whether the MST variables will be exported; defaults to --export
whether the output PATH will include the user's PATH; defaults to --fullpath (yes)
whether the output will include the an LD_LIBRARY_PATH at all; defaults to --noldlibrarypath (no)
prefix the MST variable names with the given string.
whether to output the system architecture variables; defaults to --sysarch (yes)
print a short help message and exit.
print detailed usage instructions and exit.
mst_envs is normally used inside a shell script (most likely the
user's shell startup script, like .cshrc or .profile) to add the
required entities to the user's environment to access the MST programs
and facilities. mst_envs is designed to be eval'd by the shell,
e.g.
eval `mst_envs -csh`
normally this results in the setting of various environment variables, including the user's path. To have the MST variables treated as shell variables, use the --noexport flag.
the --sysarch flag causes variables containing architecture specific info to be output. these variables are used in constructing paths in the MST enviroment. by outputing these variables, the user may make use of them at a later point without having to run the sysarch script separately.
In general, play with the options; it'll be pretty obvious what they do. Just don't eval the output until you've got what you want.
The LD_LIBRARY_PATH variable is set up to behave a bit differently from the other environment variables. Since we have chosen to avoid setting LD_LIBRARY_PATH in a user's environment in the past, if it is not present in the user's environment mst_envs will not output an LD_LIBRARY_PATH. If it is present, mst_envs with treat it much like it does PATH and MANPATH. Expect --append, --prepend, and --nofullpath to work as they would for PATH.
Diab Jerius (djerius@cfa.harvard.edu)
M Tibbetts ( mtibbetts@cfa.harvard.edu )