1SCCS(1) General Commands Manual SCCS(1)
2
6 sccs - front end for the SCCS subsystem
7
9 sccs [ -r ] [ -dpath ] [ -ppath ] command [ flags ] [ args ]
10
12 Sccs is a front end to the SCCS programs that helps them mesh more
13 cleanly with the rest of UNIX. It also includes the capability to run
14 ``set user id'' to another user to provide additional protection.
15 Basically, sccs runs the command with the specified flags and args.
17 Each argument is normally modified to be prepended with ``SCCS/s.''.
18 Flags to be interpreted by the sccs program must be before the command
20 argument. Flags to be passed to the actual SCCS program must come
21 after the command argument. These flags are specific to the command
22 and are discussed in the documentation for that command.
23 Besides the usual SCCS commands, several ``pseudo-commands'' can be
25 issued. These are:
26 edit Equivalent to ``get -e''.
28 delget Perform a delta on the named files and then get new versions.
30 The new versions will have id keywords expanded, and will not
31 be editable. The -m, -p, -r, -s, and -y flags will be passed
32 to delta, and the -b, -c, -e, -i, -k, -l, -s, and -x flags
33 will be passed to get.
34 deledit Equivalent to ``delget'' except that the ``get'' phase
36 includes the ``-e'' flag. This option is useful for making a
37 ``checkpoint'' of your current editing phase. The same flags
38 will be passed to delta as described above, and all the flags
39 listed for ``get'' above except -e and -k are passed to
40 ``edit''.
41 create Creates an SCCS file, taking the initial contents from the
43 file of the same name. Any flags to ``admin'' are accepted.
44 If the creation is successful, the files are renamed with a
45 comma on the front. These should be removed when you are
46 convinced that the SCCS files have been created successfully.
47 fix Must be followed by a -r flag. This command essentially
49 removes the named delta, but leaves you with a copy of the
50 delta with the changes that were in it. It is useful for
51 fixing small compiler bugs, etc. Since it doesn't leave
52 audit trails, it should be used carefully.
53 clean This routine removes everything from the current directory
55 that can be recreated from SCCS files. It will not remove
56 any files being edited. If the -b flag is given, branches
57 are ignored in the determination of whether they are being
58 edited; this is dangerous if you are keeping the branches in
59 the same directory.
60 unedit This is the opposite of an ``edit'' or a ``get -e''. It
62 should be used with extreme caution, since any changes you
63 made since the get will be irretrievably lost.
64 info Gives a listing of all files being edited. If the -b flag is
66 given, branches (i.e., SID's with two or fewer components)
67 are ignored. If the -u flag is given (with an optional argu‐
68 ment) then only files being edited by you (or the named user)
69 are listed.
70 check Like ``info'' except that nothing is printed if nothing is
72 being edited, and a non-zero exit status is returned if any‐
73 thing is being edited. The intent is to have this included
74 in an ``install'' entry in a makefile to insure that every‐
75 thing is included into the SCCS file before a version is
76 installed.
77 tell Gives a newline-separated list of the files being edited on
79 the standard output. Takes the -b and -u flags like ``info''
80 and ``check''.
81 diffs Gives a ``diff'' listing between the current version of the
83 program(s) you have out for editing and the versions in SCCS
84 format. The -r, -c, -i, -x, and -t flags are passed to get;
85 the -l, -s, -e, -f, -h, and -b options are passed to diff.
86 The -C flag is passed to diff as -c.
87 print This command prints out verbose information about the named
89 files.
90 The -r flag runs sccs as the real user rather than as whatever effec‐
92 tive user sccs is ``set user id'' to. The -d flag gives a root direc‐
93 tory for the SCCS files. The default is the current directory. The -p
94 flag defines the pathname of the directory in which the SCCS files will
95 be found; ``SCCS'' is the default. The -p flag differs from the -d
96 flag in that the -d argument is prepended to the entire pathname and
97 the -p argument is inserted before the final component of the pathname.
98 For example, ``sccs -d/x -py get a/b'' will convert to ``get
99 /x/a/y/s.b''. The intent here is to create aliases such as ``alias
100 syssccs sccs -d/usr/src'' which will be used as ``syssccs get
101 cmd/who.c''. Also, if the environment variable PROJECT is set, its
102 value is used to determine the -d flag. If it begins with a slash, it
103 is taken directly; otherwise, the home directory of a user of that name
104 is examined for a subdirectory ``src'' or ``source''. If such a direc‐
105 tory is found, it is used.
106 Certain commands (such as admin) cannot be run ``set user id'' by all
108 users, since this would allow anyone to change the authorizations.
109 These commands are always run as the real user.
110
112 To get a file for editing, edit it, and produce a new delta:
113 sccs get -e file.c
115 ex file.c
116 sccs delta file.c
117 To get a file from another directory:
119 sccs -p/usr/src/sccs/s. get cc.c
121 or
123 sccs get /usr/src/sccs/s.cc.c
125 To make a delta of a large number of files in the current directory:
127 sccs delta *.c
129 To get a list of files being edited that are not on branches:
131 sccs info -b
133 To delta everything being edited by you:
135 sccs delta `sccs tell -u`
137 In a makefile, to get source files from an SCCS file if it does not
139 already exist:
140 SRCS = <list of source files>
142 $(SRCS):
143 sccs get $(REL) $@
144
146 admin(SCCS), chghist(SCCS), comb(SCCS), delta(SCCS), get(SCCS),
147 help(SCCS), prt(SCCS), rmdel(SCCS), sccsdiff(SCCS), what(SCCS)
148 Eric Allman, An Introduction to the Source Code Control System
149
151 It should be able to take directory arguments on pseudo-commands like
152 the SCCS commands do.
1534.2 Berkeley Distribution May 12, 1986 SCCS(1)