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.
sccs -d/home get file.c
is interpreted as:
get /home/SCCS/s.file.c
sccs -pVERSIONS get file.c
is interpreted as:
get VERSIONS/s.file.c
Equivalent SCCS actions are indicated in parentheses.
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.
Copyright © 2003 O'Reilly & Associates. All rights reserved.