The compatibility packages include sccs, a front end to the SCCS utility. This command provides a user-friendly interface to SCCS and has the following command-line syntax:
/usr/ucb/sccs [
options
]command
[SCCS_flags
] [files
]
In addition to providing all of 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
prepath
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
endpath
Access files from directory endpath
instead of SCCS.
For example:
sccs -pVERSIONS get file.c
is interpreted as:
get VERSIONS/s.file.c
Invoke sccs as the real user instead of as the effective user.
Equivalent SCCS actions are indicated in parentheses.
Like info, but return nonzero exit codes instead of filenames.
Remove from current directory any files that aren't being edited under SCCS (via get -e, for example).
Compare file's current version and SCCS version (like sccsdiff).