usr/share/man/cat1/sccs.0

SCCS(1)                     UNIX Reference Manual                      SCCS(1)

N\bNA\bAM\bME\bE
     s\bsc\bcc\bcs\bs - front end for the SCCS subsystem

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     s\bsc\bcc\bcs\bs [-\b-r\br] [-\b-d\bd _\bp_\ba_\bt_\bh] [-\b-p\bp _\bp_\ba_\bt_\bh] _\bc_\bo_\bm_\bm_\ba_\bn_\bd [flags] [_\bf_\bi_\bl_\be ...]

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     S\bSc\bcc\bcs\bs is a front end to the SCCS programs that helps them mesh more clean-
     ly with the rest of UNIX.  It also includes the capability to run ``set
     user id'' to another user to provide additional protection.

     Basically, s\bsc\bcc\bcs\bs runs the command with the specified _\bf_\bl_\ba_\bg_\bs and _\ba_\br_\bg_\bs.  Each
     argument is normally modified to be prepended with ``SCCS/s.''.

     Flags to be interpreted by the s\bsc\bcc\bcs\bs program must be before the _\bc_\bo_\bm_\bm_\ba_\bn_\bd
     argument.  Flags to be passed to the actual SCCS program must come after
     the _\bc_\bo_\bm_\bm_\ba_\bn_\bd 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:

     e\bed\bdi\bit\bt      Equivalent to ``get -e''.

     d\bde\bel\blg\bge\bet\bt    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 -\b-m\bm, -\b-p\bp, -\b-r\br, -\b-s\bs, and -\b-y\by flags will be passed
               to d\bde\bel\blt\bta\ba, and the -\b-b\bb,\b, -\b-c\bc, -\b-e\be, -\b-i\bi, -\b-k\bk, -\b-l\bl, -\b-s\bs,
               and -\b-x\bx flags will be passed to get.

     d\bde\bel\ble\bed\bdi\bit\bt   Equivalent to d\bde\bel\blg\bge\bet\bt except that the g\bge\bet\bt phase includes the -\b-e\be
               flag.  This option is useful for making a _\bc_\bh_\be_\bc_\bk_\bp_\bo_\bi_\bn_\bt of your
               current editing phase.  The same flags will be passed to delta
               as described above, and all the flags listed for above except
               -\b-e\be and -\b-k\bk are passed to e\bed\bdi\bit\bt.

     c\bcr\bre\bea\bat\bte\be    Creates an SCCS file , taking the initial contents from the
               file of the same name.  Any flags to a\bad\bdm\bmi\bin\bn are accepted.  If
               the creation is successful, the files are renamed with a comma
               on the front.  These should be removed when you are convinced
               that the SCCS files have been created successfully.

     f\bfi\bix\bx       Must be followed by a -\b-r\br flag.  This command essentially re-
               moves 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.

     c\bcl\ble\bea\ban\bn     This routine removes everything from the current directory that
               can be recreated from SCCS files.  It will not remove any files
               being edited.  If the -\b-b\bb flag is given, branches are ignored in
               the determination of whether they are being edited; this is
               dangerous if you are keeping the branches in the same directo-
               ry.

     u\bun\bne\bed\bdi\bit\bt    This is the opposite of an e\bed\bdi\bit\bt or a ``get -e''.  It should be
               used with extreme caution, since any changes you made since the
               get will be irretrievably lost.

     i\bin\bnf\bfo\bo      Gives a listing of all files being edited.  If the -\b-b\bb flag is
               given, branches (i.e., SID's with two or fewer components) are
               ignored.  If the -\b-u\bu flag is given (with an optional argument)
               then only files being edited by you (or the named user) are
               listed.
     c\bch\bhe\bec\bck\bk     Like i\bin\bnf\bfo\bo 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
               _\bi_\bn_\bs_\bt_\ba_\bl_\bl entry in a makefile to insure that everything is in-
               cluded into the SCCS file before a version is installed.

     t\bte\bel\bll\bl      Gives a newline-separated list of the files being edited on the
               standard output.  Takes the -\b-b\bb and -\b-u\bu flags like i\bin\bnf\bfo\bo and
               c\bch\bhe\bec\bck\bk.

     d\bdi\bif\bff\bfs\bs     Gives a d\bdi\bif\bff\bf listing between the current version of the
               program(s) you have out for editing and the versions in SCCS
               format.  The -\b-r\br, -\b-c\bc, -\b-i\bi, -\b-x\bx, and -\b-t\bt flags are passed to
               g\bge\bet\bt; the -\b-l\bl, -\b-s\bs, -\b-e\be, -\b-f\bf, -\b-h\bh, and -\b-b\bb options are passed to
               d\bdi\bif\bff\bf.  The -\b-C\bC flag is passed to d\bdi\bif\bff\bf as -\b-c\bc.

     p\bpr\bri\bin\bnt\bt     This command prints out verbose information about the named
               files.

     -\b-r\br        Runs s\bsc\bcc\bcs\bs as the real user rather than as whatever effective
               user s\bsc\bcc\bcs\bs is ``set user id'' to.

     -\b-d\bd        Specifies a root directory for the SCCS files.  The default is
               the current directory.  If environment variable PROJECT is set,
               it will be used to determine the -\b-d\bd flag.

     -\b-p\bp        flag defines the pathname of the directory in which the SCCS
               files will be found; ``SCCS'' is the default.  The -\b-p\bp flag
               differs from the -\b-d\bd flag in that the -\b-d\bd argument is prepended
               to the entire pathname and the -\b-p\bp 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 a\bad\bdm\bmi\bin\bn) cannot be run ``set user id''
               by all users, since this would allow anyone to change the au-
               thorizations.  These commands are always run as the real user.

E\bEX\bXA\bAM\bMP\bPL\bLE\bES\bS
     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

     To get a file from another directory:

           sccs -p/usr/src/sccs/s. get cc.c

     or

           sccs get /usr/src/sccs/s.cc.c

     To make a delta of a large number of files in the current directory:

           sccs delta *.c

     To get a list of files being edited that are not on branches:

           sccs info -b

     To delta everything being edited by you:

           sccs delta `sccs tell -u`

     In a makefile, to get source files from an SCCS file if it does not al-
     ready exist:

           SRCS = <list of source files>
           $(SRCS):
                sccs get $(REL) $@

E\bEN\bNV\bVI\bIR\bRO\bON\bNM\bME\bEN\bNT\bT
     PROJECT     The PROJECT environment variable is checked by the -\b-d\bd flag.
                 If it begins with a slash, it is taken directly; otherwise,
                 the home directory of a user of that name is examined for a
                 subdirectory ``src'' or ``source''.  If such a directory is
                 found, it is used.

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     what(1) admin(SCCS), chghist(SCCS), comb(SCCS), delta(SCCS), get(SCCS),
     help(SCCS), prt(SCCS), rmdel(SCCS), sccsdiff(SCCS),
     Eric Allman, _\bA_\bn _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn _\bt_\bo _\bt_\bh_\be _\bS_\bo_\bu_\br_\bc_\be _\bC_\bo_\bd_\be _\bC_\bo_\bn_\bt_\br_\bo_\bl _\bS_\by_\bs_\bt_\be_\bm

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     S\bSc\bcc\bcs\bs appeared in 4.3 BSD.

B\bBU\bUG\bGS\bS
     It should be able to take directory arguments on pseudo-commands like the
     SCCS commands do.