Next: checkout, Previous: Specifying Files and Directories, Up: Subcommands
This section collects definitions of options used in
prcs subcommands. Many options have both a short form (e.g., -f
)
and a GNU-format long form (e.g., --force
); in these cases, the
long form is listed immediately below the short form. In the
descriptions below, a Standard option is one that is legal on all
subcommands, and an Option is valid on one or more subcommands.
Used in
prcs execute
to indicate that the specified command is to be executed just once, with all files as arguments.
Tells prcs to perform some optional deletion action. Used by
prcs populate
to indicate that files that are not present in a working directory are to be removed from the Files list.
Force: resolve what would normally be interactive queries in some fixed way, depending on the subcommand, assuring that prcs will never use the standard input.
Prints out help very similar to the contents of this section.
Causes certain actions to occur immediately during execution of a command. For
prcs uncompress
, causes the files in a project to be uncompressed on the spot, rather than incrementally as they are needed.
Allows prcs to spawn up to number child processes at once. Almost always, 2 or 3 will result in faster operations and higher machine load. Experimentation will yield the best results.
Causes
prcs diff
to compare keywords, instead of stripping them before comparison.
Various long formats, depending on the subcommand.
Used in
prcs execute
to indicate that the names of the files to be processed, or the options attached to them, must match pattern.
Indicates that the command is to report what would happen in the absence of `-n', without changing working files or the repository.
In
prcs diff
, produces comparisons against empty (“new”) files where a file is missing in one of the versions being compared. If you intend to use the -N option and later apply the diffs you should make sure to always use one of the context diff formats. See the PRCS_DIFF_OPTIONS environment variable See Environment Variables.
Used in
prcs execute
to indicate that the names of files to be processed, or the options attached to them, must not match pattern.
Preserve permissions on files that are checked out, ignoring any standard protections the user may have set for newly-created files (as by the file mode creation mask in UNIX).
Prevent situations where the project file may be treated as an ordinary file. For example, this causes
prcs diff
not to output changes in the project files of each version.
Turns off prcs's default formatting of its output, which is to break lines at the screen width and surround filenames with single quotes. Setting the PRCS_PLAIN_FORMAT environment variable has the same effect (see Environment Variables).
Used in
prcs execute
to indicate that directories are to be listed in pre-order: directory names first, then their non-directory contents, then subdirectories.
Identifies a version of a project. The version is a version specifier. See Version Names and Specifiers. The space between `-r' and version is optional.
Use directory as the repository, ignoring the value of the
PRCS_REPOSITORY
environment variable.
Turn off most of the safety features of
prcs merge
, allowing a skilled user finer control over the process. See merge.
Set the type of sorting for the info command to perform on its output. The two valid values for type are `version' and `date'. The default is version.
When prcs writes a working file or the project file, it generally does so by replacing any existing file of that name. With this option, however, if the file to be written is a symbolic link, that link is removed and a new file is created. Thus, the file that was originally linked to is unchanged.