SCCS(1) General Commands Manual SCCS(1)

sccs — front end for the SCCS subsystem (DEVELOPMENT)

sccs [-r][-d path][-p path] command [options ...][operands ...]

The sccs utility is a front end to the SCCS programs. It also includes the capability to run set-user-id to another user to provide additional protection.

The sccs utility invokes the specified command with the specified and operands. By default, each of the operands is modified by prefixing it with the string SCCS/s..

The command operand can be one of the SCCS utilities in this specification ( , , , , , , , or ) or one of the pseudo-utilities listed in the EXTENDED DESCRIPTION section.

The sccs utility supports the XBD specification, , except that options operands are actually options to be passed to the utility named by command . When the portion of the command:

command [options ...] [operands ...] is considered, all of the pseudo-utilities used as command support the Utility Syntax Guidelines. Any of the other SCCS utilities that can be invoked in this manner support the Guidelines to the extent indicated by their individual OPTIONS sections.

The following options are supported preceding the command operand:

A pathname of a directory to be used as a root directory for the SCCS files. The default is the current directory. The -d option takes precedence over the PROJECTDIR variable. See -p .
A pathname of a directory in which the SCCS files are located. The default is the SCCS directory. The -p option differs from the -d option in that the -d option-argument is prefixed to the entire pathname and the -p option-argument is inserted before the final component of the pathname. For example: 
sccs -d /x -p y get a/b
will convert to: 
get /x/a/y/s.b
This allows the creation of aliases such as: 
alias syssccs="sccs -d /usr/src"
which will be used as: 
syssccs get cmd/who.c
Invoke command with the real user ID of the process, not any effective user ID that the sccs utility is set to. Certain commands ( admin , check , clean , diffs , info , rmdel(1) and tell ) cannot be run set-user-ID by all users, since this would allow anyone to change the authorisations. These commands are always run as the real user.

The following operands are supported:

command
An SCCS utility name or the name of one of the pseudo-utilities listed in the EXTENDED DESCRIPTION section.
options
An option or option-argument to be passed to command .
operands
An operand to be passed to command .

See the utility description for the specified command .

See the utility description for the specified command .

The following environment variables affect the execution of sccs :

Provide a default value for the internationalisation variables that are unset or null. If LANG is unset or null, the corresponding value from the implementation-dependent default locale will be used. If any of the internationalisation variables contains an invalid setting, the utility will behave as if none of the variables had been defined.
If set to a non-empty string value, override the values of all the other internationalisation variables.
Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single- as opposed to multi-byte characters in arguments and input files).
Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
Determine the location of message catalogues for the processing of LC_MESSAGES .
Provide a default value for the -d path option. If the value of PROJECTDIR begins with a slash, it is considered an absolute pathname; otherwise, the home directory of a user of that name is examined for a src subdirectory or source . If such a directory is found, it is used. Otherwise, the value is used as a relative pathname.

Additional environment variable effects may be found in the utility description for the specified command.

Default.

See the utility description for the specified command .

See the utility description for the specified command .

See the utility description for the specified command .

The following pseudo-utilities are supported as command operands. All options referred to in the following list are values given in the options operands following command .

Equivalent to info , 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 "install" entry in a makefile to ensure that everything is included into the SCCS file before a version is installed.
Remove everything from the current directory that can be recreated from SCCS files, but do not remove any files being edited. If the -b option is given, branches are ignored in the determination of whether they are being edited; this is dangerous if branches are kept in the same directory.
Create an SCCS file, taking the initial contents from the file of the same name. Any options to admin(1) are accepted. If the creation is successful, the original files are renamed by prefixing the basenames with a comma. These renamed files should be removed after it has been verified that the SCCS files have been created successfully.
Perform a delta(1) on the named files and then get(1) new versions. The new versions will have ID keywords expanded and will not be editable. Any -m , -p , -r , -s , and -y options will be passed to delta(1) , and any -b , -c , -e , -i , -k , -l , -s and -x options will be passed to get(1) .
Equivalent to delget , except that the get(1) phase includes the -e option. This option is useful for making a checkpoint of the current editing phase. The same options will be passed to delta(1) as described above, and all the options listed for get(1) above except -e are passed to edit .
Write a difference listing between the current version of the files checked out for editing and the versions in SCCS format. Any -r , -c , -i , -x and -t options are passed to get(1) ; any -l , -s , -e , -f , -h and -b options are passed to diff(1) . A -C option is passed to diff(1) as -c .
Equivalent to get(1) -e .
Remove the named delta, but leave a copy of the delta with the changes that were in it. It is useful for fixing small compiler bugs, and so on. It must be followed by a -r SID option. Since fix doesn't leave audit trails, it should be used carefully.
Write a listing of all files being edited. If the -b option is given, branches (that is, SIDs with two or fewer components) are ignored. If a -u user option is given, then only files being edited by the named user are listed. A -U option is equivalent to -u < current user >.
Write out verbose information about the named files, equivalent to sccs prs(1) .
Write a newline-separated list of the files being edited to standard output. Takes the -b , -u and -U options like info and check .
This is the opposite of an edit or a get(1) -e . It should be used with caution, since any changes made since the get(1) will be lost.

The following exit values are returned:

Successful completion.
An error occurred.

Default.

Many of the SCCS utilities take directory names as operands as well as specific filenames. The pseudo-utilities supported by sccs are not described as having this capability, but are not prohibited from doing so.

  1. 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
  2. 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
  3. To make a delta of a large number of files in the current directory: 
    sccs delta *.c
  4. To get a list of files being edited that are not on branches: 
    sccs info -b
  5. To delta everything being edited by the current user: 
    sccs delta $(sccs tell -U)
  6. In a makefile, to get source files from an SCCS file if it does not already exist: 
    SRCS = <list of source files>
$(SRCS):
    sccs get $(REL) $@

None.

admin(1) , delta(1) , get(1) , make(1) , prs(1) , rmdel(1) , sact(1) , unget(1) , val(1) , what(1) .

February 1997 posix.fail