Definitions
Emphasized terms within a definition are defined later in this section.
- Label
- A sequence of characters used as a project name or a major
version name. It may consist of any sequence of alphanumeric
characters, and characters from
# % ^ - _ + = , .
that does not begin with a hyphen, equal-sign, or period.
- String constant
- A string (sequence) of 0 or more characters enclosed in quotation marks
(
"
). The sequence may contain any characters, including format
effectors like tabs and newline, as long as any quotation marks and
backslashes (\
) in it are stropped with a backslash. For
example,
"In DOS, you write this \"C:\\BIN\\FOO\""
- Project
- A named collection of project versions. The name may be any
label.
- Project version
- (Or version where there is no ambiguity). A directory tree of files.
The topmost directory contains a file called the project-version
descriptor. Every project version has a version name.
- Project repository (or `repository')
- A directory containing a collection of project versions each with a
unique version name, and possibly some additional administrative
information.
- Major version name
- Part of a version name. See Version Names and Specifiers.
- Minor version name
- Part of a version name. See Version Names and Specifiers.
- Version name
- A denotation for version within a project. It consists of a major
version name and a minor version name, separated by a period.
See Version Names and Specifiers.
- Version specifier
- A denotation used in the -r argument to various PRCS subcommands to
indicate one or more versions of a given project. See Version Names and Specifiers.
- Project-version descriptor
- A file containing information about project version. It always has the
base name
P.prj
, where P is the project name. These
files may also be called "descriptors" or ".prj
files."
See Descriptors.
- Working (sub)directory
- Working version
- Working files
- The term "working version" refers to a copy of a project version or to
a directory tree of files that are intended to become a project version.
The individual files are called working files. The root of a working
version's directory structure is called a working directory; it and
directories under it are called "working subdirectories." The project
version descriptor goes in the working directory.
- Ancestor version
- Each time a working version of a project is checked in,
prcs
checkin
records a list of project versions from which it was derived
(in the Parent-Version and Merge-Parents attributes of the descriptor).
This establishes a graph of project versions, each being derived from
its parents. A project version P0 is an ancestor of version
P1, if one can reach P0 from P1 by zero or more steps
along this directed, acyclic ancestry graph (thus, P1 is an
ancestor of itself). See Parent-Version attribute, Merge-Parents attribute, and merge.
- Keyword
- A project version's files may contain instances of PRCS keywords,
which
prcs checkin
replaces with appropriate text depending on
the keyword (such as the time and date of checkin, the login of the
account that checks in a version of a file, the name of the file, or the
name of the project). See Keywords.
- Internal File Identifier (or File Identifier)
- A parenthesized string that serves as a unique identifier for a version
of a file in the repository. Internal file identifiers are used in the
lists of files that appear in project-version descriptors. See Files attribute.