sccs(1)sccs(1)NAMEsccs - front-end utility program for SCCS commands
SYNOPSIS
rootpath] dirpath] command [options] [file]...
DESCRIPTION
The command is a straightforward front end to the various programs com‐
prising the Source Code Control System. It includes the capability of
running set-user-id to another user to allow shared access to the SCCS
files. reduces the need to explicitly reference the SCCS filenames.
The SCCS filenames are generated by prepending the string to the work‐
ing files specified. The default SCCS subdirectory name can be over‐
ridden with the dirpath option.
The command supplied to the command can either be an SCCS program or a
pseudo command. The SCCS programs that handles include and The pseudo
commands are:
Prints a list of all files being edited. Returns a non-zero
exit status if
a file is being edited. The intent is to allow an
'install' entry in a makefile to verify that every‐
thing is included in the SCCS file before a version
is installed. See the pseudo command for a descrip‐
tion of the and options.
Removes all files from the current directory or the named direc‐
tory
that can be recreated from the SCCS files. Does not
remove files that are in the process of being
edited. If is given, branches (i.e. SID's with
three or more components) are ignored in determining
which files are being edited. Therefore, any edits
on branches can be lost.
Creates the initial SCCS file, taking the contents from
file. Any options to are accepted. If the files
are created successfully, the original files are
renamed with a (comma) on the front. Read-only
copies are retrieved with The renamed files should
be removed after you have verified that the SCCS
files have been created successfully.
Runs on the named files and then the new versions. The
new versions of the files have expanded identifica‐
tion keywords, and cannot be edited. The options
are passed to and the options are passed to
Equivalent to
except that the phase includes the option.
Gives a listing between the current version of the files
being edited and the versions in SCCS format. The
options are passed to The options are passed to The
option is passed to as
Equivalent to
Equivalent to
except is omitted. This pseudo command is useful
when you want to run the command immediately after
creating the SCCS file.
Removes a named delta, but leaves a copy of the delta in the
current directory.
The option is required and must point to a leaf in
the source tree. Since a record of the changes is
not preserved, should be used carefully.
Lists all the files being edited. The
option ignores branches in determining which files
are being edited. The option lists only the files
being edited by user. The option is equivalent to
Prints information about named files. Equivalent to
followed by
Lists all the files being edited, with a newline after each
entry. See the
section for a description of the and options.
Equivalent to
Any changes made since the last are lost. Use with
caution.
Certain commands, and cannot use the set-user-id feature, as this would
allow anyone to change the authorizations. These commands are always
run as the real user.
Options
The options supplied to the SCCS commands are documented in the corre‐
sponding SCCS man pages. The options supplied to the pseudo commands
are documented in the above section. All other options preceding com‐
mand are documented as follows:
Runs as the real user rather than the effective user
is set-user-id to.
Gives the pathname to be used as the root directory for
the SCCS files. rootpath defaults to the current
directory. This flag takes precedence over the
environment variable.
Specifies the pathname for the SCCS files. The default is the
SCCS directory.
dirpath is appended to rootpath and is inserted
before the final component of the pathname.
The command converts to This can be used to create aliases. For exam‐
ple, the command makes an alias that can be used in commands like
EXTERNAL INFLUENCES
Environment Variables
If the environment variable is set, its value is used to determine the
option value for rootpath. If begins with a (slash), the value is used
directly; otherwise, the value is assume to be a login name and the
home directory corresponding to login name is examined for a subdirec‐
tory named or If found, this directory path is used. Otherwise, the
value is used as a relative path name.
determines the interpretation of text within file as single- and/or
multi-byte characters.
determines the language in which messages are displayed.
If or is not specified in the environment or is set to the empty
string, the value of is used as a default for each unspecified or empty
variable. If is not specified or is set to the empty string, a default
of "C" (see lang(5)) is used instead of
If any internationalization variable contains an invalid setting,
behaves as if all internationalization variables are set to "C". See
environ(5).
International Code Set Support
Single-byte and multi-byte character code sets are supported.
EXAMPLES
To create a new SCCS file:
To get a file for editing, edit it, create a new delta and get file for
editing:
To get a file from another directory
To make a delta of a large number of files in the current directory,
enter:
To get a list of files being edited that are not on branches, enter:
To get a list of files being edited by you, enter:
In a makefile, to get source files from an SCCS file if it does not
already exist, enter:
RETURN VALUE
A successful completion returns 0. On error, exists with a value from
or the exit value from the command that was invoked. The only excep‐
tion is the pseudo command which returns a non-zero exit status if a
file is being edited.
SEE ALSOadmin(1), cdc(1), comb(1), delta(1), get(1), prs(1), rmdel(1), sact(1),
sccsdiff(1), sccshelp(1), unget(1), val(1), vc(1), what(1), sccs‐
file(4).
STANDARDS CONFORMANCEsccs(1)
