NAME

checkpttool − generate or translate SCCS Mergeable delta IDs for lists of files

SYNOPSIS

checkpttool

DESCRIPTION

Checkpointtool is a graphical user interface that reads SCCS files and computes SCCS Mergeable IDs (SMIDs) for the deltas in each file using the Xerox Secure Hash Function.  A SMID consists of four eight-digit hexadecimal numbers.  At any point in time, there is a one-to-one correspondence between the SMIDs and SIDs for all the deltas in a given source file.  Source files that are manipulated by the Code Manager commands bringover(1) and resolve(1) may have their SIDs renumbered over time, but the SMIDs for the deltas do not change. 

checkpttool defines a source file to be a file filename with a corresponding SCCS file found in ./SCCS/s.filename. 

To start checkpttool, type checkpttool at a shell prompt. When checkpttool starts, the Workspace field is initialized with the value of the shell environment variable CODEMGR_WS if it is set.  If not, and if the current directory is contained within a workspace, then the Workspace field is initialized with the containing workspace.  All file names in the checkpoint file are relative to the workspace. 

To create a list of directories and files that you want archived in a checkpoint file, select the Load button which brings up a File Chooser.  Use this point-and-click chooser to create a list of directories and files in the Directories and Files pane. 

The default name of the checkpoint file is checkpt.out.  If you want a different name, edit the Checkpoint field. 

To create the checkpoint, choose the Create button. 

A checkpoint file contains one line per source file and identifies the current default delta for that source file.  Identification is not done using SCCS SIDs, because they may be renumbered by Code Manager operations.  Instead, deltas are identified by SCCS Mergeable IDs, (SMIDs) that do not change even when the SIDs are renumbered.  See checkpointfile(5) for more information. 

To extract a checkpoint, change the Category to Extract and fill in the Checkpoint and the Destination Directory fields.  If the Workspace field is not filled in, the workspace name stored in the checkpoint file will be used.  The Destination Directory must specify an empty or new directory. 

Choosing the Extract button causes a series of sccs get operations to be performed on the source files listed in the checkpoint file.  The version of each file extracted is the version specified by the SMID on its line in the checkpoint file. 

Note that the workspace used to perform an extract operation need not be the same workspace that was originally used to create the checkpoint file.  Any copy or descendant of the original workspace that contains all the source files listed in the checkpoint file will work. 

Files that have been renamed cause errors when they are encountered during extraction.  The checkpoint file does contain enough information to verify that each file found by name is the same file that held that name when the checkpoint was created.  This information can be used by users of the command-line program checkpt(1) to track down renamed files and positively identify the desired files and extract the desired deltas.  See checkpointfile(5) for more information. 

SEE ALSO

VersionTool and CheckPoint User’s Guide
checkpt(1), checkpointfile(5), bringover(1), resolve(1), sccs(1)

Sun Release 4.1  —  Last change: 01 December 1992