[Chapter 18] 18.7 sccs and Pseudo-Commands

18.7 sccs and Pseudo-Commands

The compatibility packages include sccs, a front-end to the SCCS utility. This command provides a more user-friendly interface to SCCS and has the following command-line syntax:

sccs  [options]  command  [SCCS_flags]  [files]

In addition to providing all the regular SCCS commands, sccs offers pseudo-commands. These are easy-to-use, prebuilt combinations of the regular SCCS commands. options apply only to the sccs interface. command is the SCCS command or pseudo-command to run, and SCCS_flags are specific options passed to the SCCS command being run.

sccs makes it easier to specify files because it automatically prepends SCCS/s. to any filename arguments. For example:

sccs get -e file.c

would be interpreted as:

get -e SCCS/s.file.c

Thus, when using sccs, you would first make a directory named SCCS to hold all the s. SCCS files.

18.7.1 Options

-dprepath

Locate files in prepath rather than in current directory. For example:

sccs -d/home get file.c

is interpreted as:

get /home/SCCS/s.file.c

-pendpath

Access files from directory endpath instead of SCCS. For example:

sccs -pVERSIONS get file.c

is interpreted as:

get VERSIONS/s.file.c

-r

Invoke sccs as the real user instead of as the effective user.

18.7.2 Pseudo-Commands

Equivalent SCCS actions are indicated in parentheses.

check: Like info, but return nonzero exit codes instead of filenames.
clean: Remove from current directory any files that aren't being edited under SCCS (via get -e, for example).
create: Create SCCS files (admin -i followed by get).
deledit: Same as delta followed by get -e.
delget: Same as delta followed by get.
diffs: Compare file's current version and SCCS version (like sccsdiff).
edit: Get a file to edit (get -e).
enter: Like create, but without the subsequent get (admin -i).
fix: Same as rmdel (must be followed by -r).
info: List files being edited (similar to sact).
print: Print information (like prs -e followed by get -p -m).
tell: Like info, but list one filename per line.
unedit: Same as unget.

18.7.3 Solaris Notes

SCCS is not available unless you have done at least a developer-system install.
The environment variable PROJECTDIR specifies a location where sccs searches for SCCS files. There are two possible kinds of values you can use.
An absolute pathname
sccs searches for SCCS files in the directory named by $PROJECTDIR.
A username
sccs looks in the src or source subdirectory of the given user's home directory.


18.6 Alphabetical Summary of SCCS Commands		19. The Revision Control System