�� . �� : http://www.stsci.edu/spst/lrpg/documentation/procedures/LRP_UVM_hints.html
�� : Thu Mar 29 17:09:07 2007
�� : Sun Mar 2 09:04:51 2014
��:
�� : rainbow

What is UVM?

A simple system for managing the revisions to a set of files. UVM organizes files into "elements" within UVM "libraries". Each element contains one or more "revisions" representing the changes made to that element.

Why not CVS?

CVS could certainly do the job, but I think for what we want it to do, it's a vast overkill. When you reserve a file with CVS, you get not just that file copied to your current working directory, but the whole directory structure associated with that file. This is useful when you are dealing with a large system of compiled code where you must recompile the whole system to test your change. For us, this is unneccessary. With UVM, when you check out a file, you get that file and that file only copied to your current working directory.

How is UVM currently set up on the LRP account?

With UVM, libraries can be contained within other libraries. On the LRP account, the environment variable "UVM_LIBRARY" points to the top level UVM library (the directory /data/lrp/configured/uvm).

I've put most of the files under /data/lrp/sw into UVM libraries. For most of the subdirectories found there, I created a matching UVM library.
The following libraries now exist:

doc
info
isql
lib
lisp
scripts
sqr
src

If there are other files we need to keep a revision history on, we can easily create new libraries for them.

What UVM commands to I need to know?

The most commonly used UVM commands are:

uvm reserve file_name

Reserve file_name for modification. A copy of file_name is placed in your current working directory.

uvm unreserve file_name

Unreserve file_name without replacing it.

uvm replace file_name -c "comment"

Check file_name back in. The local copy of file_name is deleted. A new copy of file_name is placed in the reference directory. "Comment" is an arbitrary string explaining the change.

uvm fetch file_name

Get a copy of the latest revision of file_name out of the library without reserving it and place it in the current working directory.

uvm create element $UVM_LIBRARY/sublibrary_name/file_name -c "comment"

Create a new element in library sublibrary_name. A copy of file_name will be placed in the reference directory.

uvm create library $UVM_LIBRARY/new_library -c "comment" -d directory

Create a new library inside $UVM_LIBRARY called new_library. "Comment" is an string explaining what new_library is all about. Directory is an optional reference directory. When files are checked into new_library, a copy will be put into this reference directory. For example, the reference directory for library $UVM_LIBRARY/doc is /data/lrp/sw/doc.

A full list of UVM commands and all the UVM documentation can be found here:
file:///home/spssoper/ucm/doc/ucm_ToC.html
(This link only works on SOGS.)

How do I set up my personal account to use UVM?

Add the following to your .setenv file:

# Set up UCM
setenv UCM_DIR /home/spssoper/ucm
setenv PATH ${PATH}:$UCM_DIR/bin:$UCM_DIR/bin/SunOS/
alias guvm "wish -f $UCM_DIR/bin/uvm.tcl"

# Set our default UVM library silently
setenv UVM_LIBRARY "$LRP_DIR/configured/uvm"
uvm default $UVM_LIBRARY