sccs - Administration program for Source Code Control System
(SCCS) commands
sccs [-r] [-d pathname] [-p pathname] command [commandopts...]
[parameters...]
Interfaces documented on this reference page conform to
industry standards as follows:
sccs: XCU5.0
Refer to the standards(5) reference page for more information
about industry standards and associated tags.
Specifies a root directory for the SCCS files. The
default is the current directory. The pathname argument is
prepended to the entire path name of a file. This option
takes precedence over the PROJECTDIR variable. Specifies
a path name for the SCCS files. The default is the SCCS
directory.
The pathname argument associated with the -d option
is inserted before the entire path name. The pathname
argument associated with the -p option is
inserted before the final component of the path
name. For example, the command
sccs -d/x -py get a/b converts to get /x/a/y/s.b.
This can be used to create aliases. See the first
entry in the EXAMPLES section. Runs the sccs command
as the real user, rather than as the effective
user to which the sccs command is set. Certain commands
(admin, check, clean, diffs, info, rmdel,
sccsdiff, tell) 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.
SCCS command or pseudocommand listed in the DESCRIPTION
section to be executed. Options for the specified command
or pseudocommand.
All options specified after command are passed to
that command during execution. (For a description
of command options, see the appropriate command
description.) Parameters (usually file or directory
path names) for the specified command or pseudocommand.
All parameters specified after command are passed
to that command during execution. (For a description
of command parameters, see the appropriate
command description.)
The sccs command is an administration program that incorporates
the set of SCCS commands into the operating system.
[Tru64 UNIX] The sccs command can be used to assign or
reassign file ownership.
The sccs command activates a specified command with the
specified options and arguments. Each file is placed in a
directory named SCCS and named s.filename. The directory
SCCS is assumed to exist relative to the current directory
(unless the -p option is used).
Two types of commands can be used in the sccs command syntax
sentence.
SCCS Commands [Toc] [Back]
The first type is the sccs commands that can be entered at
a prompt. For a description of the command, options, and
parameters, see the reference page with same name as the
command. Function Creates and initializes or changes
(administer) SCCS files. [Tru64 UNIX] Changes the comments
in a Source Code Control System (SCCS) delta.
[Tru64 UNIX] Combines Source Code Control System (SCCS)
deltas. Saves editing changes in a Source Code Control
System (SCCS) file. Creates a specified version of a
Source Code Control System (SCCS) file. Displays key
information in a Source Code Control System (SCCS) file.
Removes a delta from a Source Code Control System (SCCS)
file. Displays current Source Code Control System (SCCS)
file editing status. [Tru64 UNIX] Compares two versions
of a Source Code Control System (SCCS) file. [Tru64
UNIX] Provides information about a Source Code Control
System (SCCS) message or command. Cancels a previous get
command Validates Source Code Control System (SCCS) files.
Displays identifying information for Source Code Control
System (SCCS) files.
Pseudocommands [Toc] [Back]
The second type is called pseudocommands; they can be used
only as part of the sccs command syntax. These pseudocommands,
the actions they perform, options and parameters
are: Description Prints all the files being edited.
Returns a nonzero exit status if a file is being edited.
The check program puts the nonzero status indicator in an
install entry in a makefile to verify that the SCCS file
is complete before installing a version. Equivalent to
info except that nothing is printed if nothing is being
edited.
Options: Ignores branches in determining which
files are being edited. Lists only the files being
edited by you or the user named by user. Equivalent
to specifying -u <your login name>. Removes
from the current directory or the named directory
all files that can be recreated from SCCS files.
Does not remove files that are in the process of
being edited.
Option: Ignores branches in determining which files
are being edited. (Note: branches in the same
directory can be lost.) Creates an SCCS file,
copying the initial contents from a file of the
same name. If the file creation is successful, the
original file is renamed with a comma on the front.
It is recommended, but not necessary, that you to
move or remove the original file (as is the case
with the admin command).
Options:
Accepts the same options as the admin command. See
the admin(1) reference page. Performs a delta command
on the named files and then gets a new version.
The new version of the files has expanded
identification keywords, and cannot be edited.
Options: Can be passed to the delta command. See
the delta(1) reference page. Can be passed to the
get command. See the get(1) reference page.
Equivalent to the delget pseudocommand, except that
the get portion of the sentence includes the -e
option. The deledit option is useful for creating a
checkpoint in your current editing session.
Options: Can be passed to the delta command. See
the delta(1) reference page. Can be passed to the
get command. See the get(1) reference page. Shows
the difference between the current version of the
files you are editing and the versions in SCCS format.
Options: Can be passed to the get command. See the
get(1) reference page. Can be passed to the system
diff (not SCCS) command. See the diff(1) reference
page. Can be passed to the system diff (not SCCS)
command as a -c option. See the diff(1) reference
page. Equivalent to the get -e command. [Tru64
UNIX] Creates an SCCS file, copying the initial
contents from a file of the same name. If the file
creation is successful, the original file is
renamed with a , (comma) at the beginning of the
old file name. This pseudocommand is similar to
create, except that enter does not perform the
equivalent of an SCCS get command, and retrieves a
read-only version of the newly created file. This
pseudocommand is useful when you want to use an
SCCS edit command immediately after creating an
SCCS file. Removes a named delta, but leaves a
copy of the delta with changes intact. This copy
is useful for fixing small compilation errors.
This command does not keep a record of changes made
to the file. The fix command must include -r SID.
Option: Specifies the delta to be removed. Lists
all the files being edited.
Options: Ignores branches in determining which
files are being edited. Lists only the files being
edited by you or the user named by user. Equivalent
to specifying -u <your login name>. Prints
information about named files. This SCCS pseudocommand
is equivalent to the SCCS command prs.
Lists, on standard output, all the files being
edited, with a newline after each entry.
Options: Ignores branches in determining which
files are being edited. Lists only the files being
edited by you or the user named by user. Equivalent
to specifying -u <your login name>.
Equivalent to the unget command. Any changes made
since the get command was used are lost.
[Tru64 UNIX] In some other versions of the utility, the
command runs with the UID of a pseudo-user named sccs.
This difference can create compatibility problems with
permissions, especially in networked environments.
The following exit values are returned: Successful completion.
An error occurred.
Enter the command: alias syssccs sccs -d/usr/abc/sccs
This makes syssccs an alias that can be used in
commands like: syssccs get cmd/who.c To get a file
for editing, edit it, and produce a new delta,
enter: $ sccs get -e file.c $ ex file.c $ sccs
delta file.c To get a file from another directory,
enter: sccs -p/usr/abc/sccs get cc.c To make a
delta of a large number of files in the current
directory, enter: sccs delta *.c To get a list of
files being edited that are not on branches, enter:
sccs info -b To make a delta of everything being
edited by you, enter: sccs delta `sccs tell -u` In
a makefile, to get source files from an SCCS file
if it does not already exist, enter: REL = 1.7 SRCS
= <list of source files> $(SRCS):
sccs get $(REL) $@
ENVIRONMENT VARIABLES [Toc] [Back] The following environment variables affect the execution
of sccs: Provides a default value for the internationalization
variables that are unset or null. If LANG is unset
or null, the corresponding value from the default locale
is used. If any of the internationalization variables
contain an invalid setting, the utility behaves as if none
of the variables had been defined. If set to a non-empty
string value, overrides the values of all the other internationalization
variables. Determines the locale for the
interpretation of sequences of bytes of text data as characters
(for example, single-byte as opposed to multibyte
characters in arguments and input files). Determines the
locale for the format and contents of diagnostic messages
written to standard error. Determines the location of
message catalogs for the processing of LC_MESSAGES. If
this is set, its value is used to determine the -d option
value. If PROJECTDIR begins with a / (slash), the value is
used directly; otherwise, the home directory of a user of
that name is examined for a subdirectory named src or
source. If found, that subdirectory is used. The -d
option takes precedence over this variable.
Commands: admin(1), cdc(1), comb(1), delta(1), get(1),
make(1), make(1p), make(1u), prs(1), rmdel(1), sact(1),
sccsdiff(1), sccshelp(1), unget(1), val(1), what(1)
Files: sccsfile(4)
Standards: standards(5)
Programming Support Tools
[ Back ] |
