A magic file contains an ordered set of file-typing rules, which ClearCase uses to determine a list of file types for an existing file system object, or for one that is about to be created. A rule can use the object's name, its stat data, or its contents. File-typing involves searching one or more magic files for the first rule that matches a file-system object; finding a match yields a single file type or an ordered list of file types; failing to find a match produces an error.
ClearCase performs file-typing when you create a new element with mkelem, but do not specify an element type (with -eltype). (If you are converting a view-private file to an element with mkelem -ci or mkelem -nco, the file's contents are also used in the file-typing.) The resulting file type list is compared with the VOB's set of element types (which includes both element types in the VOB and element types in the Admin VOB hierarchy associated with the VOB). The first file type that matches an element type is chosen as the element type; if no file type matches any existing element type, an error occurs:
cleartool: Error: Can't pick element type from rules ...
Following are examples of file-typing rules:
directory : -stat d ;
c_source source text_file : -printable & -name "*.c" ;
sh_script script text_file : -printable & (-name ".profile" | -name "*.sh") ;
archive library file: !-printable & -name "*.a" ;
ClearCase supports a search path for magic files. If MAGIC_PATH is set in your environment (to a semicolon-separated list of directories), ClearCase searches files with a .magic extension in these directories. In each directory, files are processed in alphabetical order. As soon as ClearCase finds a matching rule, the search ends. If multiple rules match a file type, the first rule encountered is used.
If MAGIC_PATH is not set, this default search path is used:
%HOME%\.magic;ccase-home-dir\config\magic
Each file-typing rule has the following format:
file-type-list : selection-expression ;
A single text line can contain multiple rules. Conversely, a single rule can span several lines; each intermediate line must end with a backslash (\). A line that begins with a number sign (#) is a comment.
NOTE: The semicolon (;) that terminates a rule must be separated from the preceding characters by white space.
A file-type-list is an ordered list of one or more names, separated by white space. Only letters, digits, and underscores ( _ ) are permitted in these names. Depending on the file-typing situation, each name must match either an element type defined in some VOB, or an icon name specified in an icon file. To avoid errors, always make the final name one of ClearCase's predefined element types (see Predefined Element Types in the mkeltype reference page). These names are also included in the system-default icon file.
Following are some file-type-list examples:
text_file
backup_dir directory
manual_page text_file
cplusplus_src src_file text_file
Here is a scenario that calls for a lengthy file type list:
Your host mounts several VOBs, in which different sets of element types are defined. Perhaps one VOB defines element type pscript for Perl scripts, a second VOB defines element type batch_file for all shell scripts, and a third VOB does not define any special element type for scripts. Your file-typing rules must be appropriate for all the VOBs. For example:
pscript batch_file text_file : -name "*.pl" ;
batch_file text_file : -name "*.bat" ;
pscript batch_file text_file : -name "*.pl" ;
shscript batch_file text_file : -name "*.sh" ;
A selection-expression consists of one or more selection operators and their arguments, connected by
logical operators. Examples:
-name "*.c"
-name "*.[ch]"
-name "*.c" | -name "*.h"
-printable
!-printable
-stat d
Any abbreviation of a selection operator name is accepted. For example, you can abbreviate -name to -n, -na, or -nam.
All string arguments must be enclosed in double quotes. Use \" to include a double-quote character in a string argument.
If the file-system object already exists, any of the selection operators listed below can produce a match. If you are determining the file type for a nonexistent object (for example, an element that is about to be created with mkelem), only the -name operator can produce a match.
r | Regular file |
d | Directory |
c | Character device; not supported for Windows files |
b | Block device; not supported for Windows files |
f | FIFO (named pipe); not supported for Windows files |
s | Socket; not supported for Windows files |
l | Symbolic link |
byte_offset | The byte offset from the beginning of the file. | |
data_type | The architecture-specific data format of the numeric value argument that follows: | |
byte | value is an 8-bit byte. | |
l_short | value is a little-endian 16-bit shortword. | |
l_long | value is a little-endian 32-bit longword. | |
b_short | value is a big-endian 16-bit shortword. | |
b_long | value is a big-endian 32-bit longword. | |
value | A numeric magic value, expressed as an integer in hexadecimal, octal, or decimal: | |
0x ... | A hexadecimal value | |
0 ... | An octal value | |
... | (Any other form) A decimal value | |
string | A nonnumeric magic value, expressed as a double-quoted string. | |
|
|
File-typing rules can use the following logical operators, listed in decreasing order of precedence:
(0) | Parentheses for grouping |
! | Unary NOT |
& | Logical AND |
&& | Logical AND |
| | Logical OR |
|| | Logical OR |
NOTE: The effect of the unary NOT operator may depend on whether or not an object exists. It cannot produce a match if the selection operator is inappropriate.
source_file text_file : -name "*.c" | -name "*.h" ;
cplspls_source text_file : -printable & (-name "*.cxx" | -name "*.c++") ;
csh_script text_file : -printable & -magic 0,"#!" & -token "csh" ;
directory : -stat d ;
doc_file text_file : -printable & (-name "*.doc" | -name "*.txt");
ccase-home-dir\config\magic\default.magic
mkelem, mkeltype, wildcards_ccase
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 1999 by Rational Software Corporation. All rights reserved. |