Intel XENIX 286 Programmers Guide (86) - Tenox.tc

SCCS: Source Code Control System XENIX Programming
SCCS Command Argu ments
Almost all SCCS commands accept two types of arguments: options and file names.
These appear in the sees command line immediately after the command name.
An option indicates a special action to be taken by the given sees command. An option
is usually a lowercase letter preceded by a hyphen (-). Some options require an
additional name or value.
A file name indicates the file to be acted on. The syntax for sees file names is like
other XENIX file names. Appropriate path names must be given if required. Some
commands also allow directory names. In this case, all files in the directory are acted
on. If the directory contains non-sees or unreadable files, these are ignored. A file
name must not begin with a hyphen (-).
The special symbol - may be used to cause an SCCS command to read a list of file
names from the standard input. These file names are then used as names for the files to
be processed. The list must be terminated by the end-of-file character CONTROL-D.
Any options given with a command apply to all files. The sees commands process the
options before any file names so the options may appear anywhere on the command line.
File names are processed left to right. If a command encounters a fatal error, it stops
processing the current file and, if any other files have been given, begins processing the
next.
File Administrator
Every SCCS file requires an administrator to maintain and keep the file in order. The
adm inistrator is usually the user who created the file and therefore owns the file. When
other users intend to access the file, the administrator must ensure that they have
adequate access. Several SCCS commands are used by the administrator to define who
has access to the versions in a given s-file. These commands are described later.
Creating and Using s-files
The s-file is the key element in SCCS. It provides compact storage for all versions of a
given file and automatic maintenance of the relationships between the versions.
This section explains how to use the admin, get, and delta commands to create and use
s-files. In particular, it describes how to create the first version of a file, how to
retrieve versions for reading and editing, and how to save new versions.
5-4