C sccs - front end for the SCCS subsystem sccs [ -r ] [ -d path ] [ -p path ] command [ flags ] [ args ] Sccs is a front end to the SCCS programs that help them mesh more cleanly with the rest of UNIX. It also includes the capability to run ``set user id'' to another user to provide additional protection.

Basically, sccs runs the command with the specified flags and args. Each argument is normally modified to be prepended with ``SCCS/s.''.

Flags to be interpreted by the sccs program must be before the command argument. Flags to be passed to the actual SCCS program must come after the command argument. These flags are specific to the command and are discussed in the documentation for that command.

Besides the usual SCCS commands, several ``pseudo-commands'' can be issued. These are:

Equivalent to ``get -e''. Perform a delta on the named files and then get new versions. The new versions will have id keywords expanded, and will not be editable. The -m, -p, -r, -s, and -y flags will be passed to delta, and the -b, -c, -e, -i, -k, -l, -s, and -x flags will be passed to get. Equivalent to ``delget'' except that the ``get'' phase includes the ``-e'' flag. This option is useful for making a ``checkpoint'' of your current editing phase. The same flags will be passed to delta as described above, and all the flags listed for ``get'' above except -e and -k are passed to ``edit''. Must be followed by a -r flag. This command essentially removes the named delta, but leaves you with a copy of the delta with the changes that were in it. It is useful for fixing small compiler bugs, etc. Since it doesn't leave audit trails, it should be used carefully. Takes no arguments. This routine removes everything from the current directory that can be recreated from SCCS files. It will not remove any files being edited. This is the opposite of an ``edit'' or a ``get -e''. It should be used with extreme caution, since any changes you made since the get will be irretrievably lost. Gives a listing of all files being edited. Like ``info'' except that nothing is printed if nothing is being edited, and a non-zero exit status is returned if anything is being edited. The intent is to have this included in an ``install'' entry in a makefile to insure that everything is included into the SCCS file before a version is installed.

The -r flag runs sccs as the real user rather than as whatever effective user sccs is ``set user id'' to. The -d flag gives a root directory for the SCCS files. The default is the current directory. The -p flag defines the pathname of the directory in which the SCCS files will be found; ``SCCS'' is the default. The -p flag differs from the -d flag in that the -d argument is prepended to the entire pathname and the -p argument is inserted before the final component of the pathname. For example, ``sccs -d/x -py get a/b'' will convert to ``get /x/a/y/s.b''. The intent here is to create aliases such as ``alias syssccs sccs -d/usr/src'' which will be used as ``syssccs get cmd/who.c''.

Certain commands (such as admin ) cannot be run ``set user id'' by all users, since this would allow anyone to change the authorizations. These commands are always run as the real user.

..

.. To get a file for editing, edit it, and produce a new delta: sccs get -e file.c ex file.c sccs delta file.c .EX To get a file from another directory: sccs -p/usr/src/sccs/s. get cc.c .EX or sccs get /usr/src/sccs/s.cc.c .EX To make a delta of a large number of files in the current directory: sccs delta *.c .EX In a makefile, to get source files from an SCCS file if it does not already exist: SRCS = <list of source files> $(SRCS): sccs get $(REL) $@ .EX

admin(SCCS), chghist(SCCS), comb(SCCS), delta(SCCS), get(SCCS), help(SCCS), prt(SCCS), rmdel(SCCS), sccsdiff(SCCS), what(SCCS)

Eric Allman, .ul An Introduction to the Source Code Control System

Since it is not yet clear what this program should do, it should not be considered a stable program product. Please send any comments & suggestions to csvax:eric.