[Chapter 17] 17.6 sccs and Pseudo-commands

17.6 sccs and Pseudo-commands

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

17.6.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.

17.6.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 .