1SCCS(1P) POSIX Programmer's Manual SCCS(1P)
2
6 This manual page is part of the POSIX Programmer's Manual. The Linux
7 implementation of this interface may differ (consult the corresponding
8 Linux manual page for details of Linux behavior), or the interface may
9 not be implemented on Linux.
10
12 sccs - front end for the SCCS subsystem (DEVELOPMENT)
13
15 sccs [-r][-d path][-p path] command [options...][operands...]
16
18 The sccs utility is a front end to the SCCS programs. It also includes
19 the capability to run set-user-id to another user to provide additional
20 protection.
21 The sccs utility shall invoke the specified command with the specified
23 options and operands. By default, each of the operands shall be modi‐
24 fied by prefixing it with the string "SCCS/s." .
25 The command can be the name of one of the SCCS utilities in this volume
27 of IEEE Std 1003.1-2001 ( admin, delta, get, prs, rmdel, sact, unget,
28 val, or what) or one of the pseudo-utilities listed in the EXTENDED
29 DESCRIPTION section.
30
32 The sccs utility shall conform to the Base Definitions volume of
33 IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines, except
34 that options operands are actually options to be passed to the utility
35 named by command. When the portion of the command:
36 command [options ... ] [operands ... ]
39 is considered, all of the pseudo-utilities used as command shall sup‐
41 port the Utility Syntax Guidelines. Any of the other SCCS utilities
42 that can be invoked in this manner support the Guidelines to the extent
43 indicated by their individual OPTIONS sections.
44 The following options shall be supported preceding the command operand:
46 -d path
48 A pathname of a directory to be used as a root directory for the
49 SCCS files. The default shall be the current directory. The -d
50 option shall take precedence over the PROJECTDIR variable. See
51 -p.
52 -p path
54 A pathname of a directory in which the SCCS files are located.
55 The default shall be the SCCS directory.
56 The -p option differs from the -d option in that the -d option-argument
58 shall be prefixed to the entire pathname and the -p option-argument
59 shall be inserted before the final component of the pathname. For exam‐
60 ple:
61 sccs -d /x -p y get a/b
64 converts to:
66 get /x/a/y/s.b
69 This allows the creation of aliases such as:
71 alias syssccs="sccs -d /usr/src"
74 which is used as:
76 syssccs get cmd/who.c
79 -r Invoke command with the real user ID of the process, not any
81 effective user ID that the sccs utility is set to. Certain com‐
82 mands ( admin, check, clean, diffs, info, rmdel, and tell) can‐
83 not be run set-user-ID by all users, since this would allow any‐
84 one to change the authorizations. These commands are always run
85 as the real user.
86
89 The following operands shall be supported:
90 command
92 An SCCS utility name or the name of one of the pseudo-utilities
93 listed in the EXTENDED DESCRIPTION section.
94 options
96 An option or option-argument to be passed to command.
97 operands
99 An operand to be passed to command.
100
103 See the utility description for the specified command.
104
106 See the utility description for the specified command.
107
109 The following environment variables shall affect the execution of sccs:
110 LANG Provide a default value for the internationalization variables
112 that are unset or null. (See the Base Definitions volume of
113 IEEE Std 1003.1-2001, Section 8.2, Internationalization Vari‐
114 ables for the precedence of internationalization variables used
115 to determine the values of locale categories.)
116 LC_ALL If set to a non-empty string value, override the values of all
118 the other internationalization variables.
119 LC_CTYPE
121 Determine the locale for the interpretation of sequences of
122 bytes of text data as characters (for example, single-byte as
123 opposed to multi-byte characters in arguments and input files).
124 LC_MESSAGES
126 Determine the locale that should be used to affect the format
127 and contents of diagnostic messages written to standard error.
128 NLSPATH
130 Determine the location of message catalogs for the processing of
131 LC_MESSAGES .
132 PROJECTDIR
134 Provide a default value for the -d path option. If the value of
136 PROJECTDIR begins with a slash, it shall be considered an abso‐
137 lute pathname; otherwise, the value of PROJECTDIR is treated as
138 a user name and that user's initial working directory shall be
139 examined for a subdirectory src or source. If such a directory
140 is found, it shall be used. Otherwise, the value shall be used
141 as a relative pathname.
142 Additional environment variable effects may be found in the utility
145 description for the specified command.
146
148 Default.
149
151 See the utility description for the specified command.
152
154 See the utility description for the specified command.
155
157 See the utility description for the specified command.
158
160 The following pseudo-utilities shall be supported as command operands.
161 All options referred to in the following list are values given in the
162 options operands following command.
163 check Equivalent to info, except that nothing shall be printed if
165 nothing is being edited, and a non-zero exit status shall be
166 returned if anything is being edited. The intent is to have this
167 included in an "install" entry in a makefile to ensure that
168 everything is included into the SCCS file before a version is
169 installed.
170 clean Remove everything from the current directory that can be recre‐
172 ated from SCCS files, but do not remove any files being edited.
173 If the -b option is given, branches shall be ignored in the
174 determination of whether they are being edited; this is danger‐
175 ous if branches are kept in the same directory.
176 create Create an SCCS file, taking the initial contents from the file
178 of the same name. Any options to admin are accepted. If the cre‐
179 ation is successful, the original files shall be renamed by pre‐
180 fixing the basenames with a comma. These renamed files should be
181 removed after it has been verified that the SCCS files have been
182 created successfully.
183 delget Perform a delta on the named files and then get new versions.
185 The new versions shall have ID keywords expanded and shall not
186 be editable. Any -m, -p, -r, -s, and -y options shall be passed
187 to delta, and any -b, -c, -e, -i, -k, -l, -s, and -x options
188 shall be passed to get.
189 deledit
191 Equivalent to delget, except that the get phase shall include
192 the -e option. This option is useful for making a checkpoint of
193 the current editing phase. The same options shall be passed to
194 delta as described above, and all the options listed for get
195 above except -e shall be passed to edit.
196 diffs Write a difference listing between the current version of the
198 files checked out for editing and the versions in SCCS format.
199 Any -r, -c, -i, -x, and -t options shall be passed to get; any
200 -l, -s, -e, -f, -h, and -b options shall be passed to diff. A -C
201 option shall be passed to diff as -c.
202 edit Equivalent to get -e.
204 fix Remove the named delta, but leave a copy of the delta with the
206 changes that were in it. It is useful for fixing small compiler
207 bugs, and so on. The application shall ensure that it is fol‐
208 lowed by a -r SID option. Since fix does not leave audit trails,
209 it should be used carefully.
210 info Write a listing of all files being edited. If the -b option is
212 given, branches (that is, SIDs with two or fewer components)
213 shall be ignored. If a -u user option is given, then only files
214 being edited by the named user shall be listed. A -U option
215 shall be equivalent to -u< current user>.
216 print Write out verbose information about the named files, equivalent
218 to sccs prs.
219 tell Write a <newline>-separated list of the files being edited to
221 standard output. Takes the -b, -u, and -U options like info and
222 check.
223 unedit This is the opposite of an edit or a get -e. It should be used
225 with caution, since any changes made since the get are lost.
226
229 The following exit values shall be returned:
230 0 Successful completion.
232 >0 An error occurred.
234
237 Default.
238 The following sections are informative.
240
242 Many of the SCCS utilities take directory names as operands as well as
243 specific filenames. The pseudo-utilities supported by sccs are not
244 described as having this capability, but are not prohibited from doing
245 so.
246
248 1. To get a file for editing, edit it and produce a new delta:
249 sccs get -e file.c
252 ex file.c
253 sccs delta file.c
254 2. To get a file from another directory:
256 sccs -p /usr/src/sccs/s. get cc.c
259 or:
261 sccs get /usr/src/sccs/s.cc.c
264 3. To make a delta of a large number of files in the current direc‐
266 tory:
267 sccs delta *.c
270 4. To get a list of files being edited that are not on branches:
272 sccs info -b
275 5. To delta everything being edited by the current user:
277 sccs delta $(sccs tell -U)
280 6. In a makefile, to get source files from an SCCS file if it does not
282 already exist:
283 SRCS = <list of source files>
286 $(SRCS):
287 sccs get $(REL) $@
288
290 SCCS and its associated utilities are part of the XSI Development Util‐
291 ities option within the XSI extension.
292 SCCS is an abbreviation for Source Code Control System. It is a mainte‐
294 nance and enhancement tracking tool. When a file is put under SCCS, the
295 source code control system maintains the file and, when changes are
296 made, identifies and stores them in the file with the original source
297 code and/or documentation. As other changes are made, they too are
298 identified and retained in the file.
299 Retrieval of the original and any set of changes is possible. Any ver‐
301 sion of the file as it develops can be reconstructed for inspection or
302 additional modification. History data can be stored with each version,
303 documenting why the changes were made, who made them, and when they
304 were made.
305
307 None.
308
310 admin, delta, get, make, prs, rmdel, sact, unget, val, what
311
313 Portions of this text are reprinted and reproduced in electronic form
314 from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology
315 -- Portable Operating System Interface (POSIX), The Open Group Base
316 Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
317 Electrical and Electronics Engineers, Inc and The Open Group. In the
318 event of any discrepancy between this version and the original IEEE and
319 The Open Group Standard, the original IEEE and The Open Group Standard
320 is the referee document. The original Standard can be obtained online
321 at http://www.opengroup.org/unix/online.html .
322IEEE/The Open Group 2003 SCCS(1P)