CLI User's Guide - AccuRev

add
Using Triggers to Control the Element Type and Exclusive File Locking State
Setting of the element type or the exclusive file locking state (or both) can be automated with
triggers. Settings made by triggers scripts override the add -E specifications, if any.
• To set the element type based on file extensions and/or file content, set a pre-operation trigger
with mktrig pre-create-trig. AccuRev ships with a sample trigger script, elem_type.pl. You
can customize it to recognize new file suffixes.
• To set the exclusive file locking state on a file-by-file basis, use the server-side pre-operation
trigger, admin_preop_trig.
These triggers are fully described in AccuRev Triggers on page 71 of the AccuRev Administrator’s
Guide.
How AccuRev Handles File Elements of Different Types
AccuRev handles binary files very simply: when a new binary version is created (with add or
keep), AccuRev simply copies the file from your workspace tree to the repository, creating a
storage file. When you retrieve a binary file from the repository (for example, with co -v or
update), AccuRev simply copies the storage file to your workspace tree.
Handling of text files is more sophisticated. By default:
• When a new version is created (add or keep), a new storage file is placed in the repository,
with a single NL (or LF) character (hex character code x0A) at the end of each text line. This
means that a version’s storage file may have different line terminators than the file you
submitted to the add or keep command.
• When a text file is copied into the workspace by an AccuRev command (e.g. update, pop), it
gets the line terminators appropriate to the machine where the workspace is located: NL (x0A)
for a UNIX/Linux machine, or CR-NL (x0D x0A) for a Windows machine.
On the individual element level, you can override the manipulation of line terminators by
specifying the “preserve text line terminators” element type, with the -E ptext option. Files of this
type are copied to and from the repository with no change, just like binary files.
On the workspace level, you can force the use of a particular line terminator when text files are
copied to the workspace, using the -e option to mkws or chws. This applies to all elements of type
text, but not to elements of type ptext.
How AccuRev Converts Existing Links to Link Elements
The add command converts existing link objects with (external) status to AccuRev elements as
follows:
• An existing hard link is always converted to an AccuRev file element.
• An existing symbolic link (UNIX/Linux) or junction point (Windows) is converted to an
AccuRev element-link element (elink) in these circumstances:
• The target is a file element, directory element, or elink in your workspace, and you omit
the -s command-line option. (If the target is an slink, you must use -s to convert the object
to an slink. You cannot create an elink that points to an slink.)
AccuRev® CLI User’s Guide 41