Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Reference > S

sccs(1)

HP-UX 11i Version 3: February 2007
» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

NAME

sccs — front-end utility program for SCCS commands

SYNOPSIS

sccs [-r] [-d rootpath] [-p dirpath] command [options] [file]...

DESCRIPTION

The sccs command is a straightforward front end to the various programs comprising 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. sccs reduces the need to explicitly reference the SCCS filenames. The SCCS filenames are generated by prepending the string SCCS/s. to the working files specified. The default SCCS subdirectory name can be overridden with the -p dirpath option.

The command supplied to the sccs command can either be an SCCS program or a pseudo command. The SCCS programs that sscs handles include admin, cdc, comb, delta, get, help, prs, rmdel, sact, unget, val, what and sccsdiff. The pseudo commands are:

check

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 everything is included in the SCCS file before a version is installed. See the info pseudo command for a description of the -b, -u user and -U options.

clean

Removes all files from the current directory or the named directory that can be recreated from the SCCS files. Does not remove files that are in the process of being edited. If -b 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.

create

Creates the initial SCCS file, taking the contents from file. Any options to admin 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 get. The renamed files should be removed after you have verified that the SCCS files have been created successfully.

delget

Runs delta on the named files and then get the new versions. The new versions of the files have expanded identification keywords, and cannot be edited. The [-mprsy] options are passed to delta, and the [-bceiklsx] options are passed to get.

deledit

Equivalent to delget, except that the get phase includes the -e option.

diffs

Gives a diff listing between the current version of the files being edited and the versions in SCCS format. The [-rcixt] options are passed to get. The [-lsefhb] options are passed to diff. The -C option is passed to diff as -c.

edit

Equivalent to get -e.

enter

Equivalent to create, except get is omitted. This pseudo command is useful when you want to run the edit command immediately after creating the SCCS file.

fix

Removes a named delta, but leaves a copy of the delta in the current directory. The -r SID option is required and must point to a leaf in the source tree. Since a record of the changes is not preserved, fix should be used carefully.

info

Lists all the files being edited. The -b option ignores branches in determining which files are being edited. The -u user option lists only the files being edited by user. The -U option is equivalent to -u current_user.

print

Prints information about named files. Equivalent to prs -a followed by get -p -m -s.

tell

Lists all the files being edited, with a newline after each entry. See the info section for a description of the -b, -u user and -U options.

unedit

Equivalent to unget. Any changes made since the last get are lost. Use with caution.

Certain commands, admin, cdc, check, clean, diffs, info, rmdel, sccsdiff, and tell 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 corresponding SCCS man pages. The options supplied to the pseudo commands are documented in the above section. All other options preceding command are documented as follows:

-r

Runs sccs as the real user rather than the effective user sccs is set-user-id to.

-d rootpath

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 PROJECTDIR environment variable.

-p dirpath

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 sccs -d /usr -p cmd get src/b converts to get/usr/src/cmd/s.b. This can be used to create aliases. For example, the command alias syssccs="sccs -p /usr/src/cmd" makes syssccs an alias that can be used in commands like syssccsgetb.

EXTERNAL INFLUENCES

Environment Variables

If the PROJECTDIR environment variable is set, its value is used to determine the -d rootpath option value for rootpath. If PROJECTDIR 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 subdirectory named src or source. If found, this directory path is used. Otherwise, the value is used as a relative path name.

LC_CTYPE determines the interpretation of text within file as single- and/or multi-byte characters.

LC_MESSAGES determines the language in which messages are displayed.

If LC_CTYPE or LC_MESSAGES is not specified in the environment or is set to the empty string, the value of LANG is used as a default for each unspecified or empty variable. If LANG is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of LANG.

If any internationalization variable contains an invalid setting, sccs 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:

sccs create file

To get a file for editing, edit it, create a new delta and get file for editing:

sccs edit file.c ex file.c sccs deledit file.c

To get a file from another directory (/usr/src/cmd/SCCS/s.cc.c):

sccs -d /usr/src get cmd/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 get a list of files being edited by you, enter:

sccs tell -u

In a makefile, to get source files from an SCCS file if it does not already exist, enter:

SRCS = <list of source files> $ (SRCS) : sccs get $(REL) $@

RETURN VALUE

A successful completion returns 0. On error, sccs exists with a value from <sysexits.h> or the exit value from the command that was invoked. The only exception is the check pseudo command which returns a non-zero exit status if a file is being edited.

STANDARDS CONFORMANCE

sccs: XPG4

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1983-2007 Hewlett-Packard Development Company, L.P.