Converts RCS files to elements
Product | Command Type |
---|---|
ClearCase | command |
ClearCase LT | command |
Platform |
---|
UNIX |
Windows |
The clearexport_rcs command processes Revision Control System (RCS) files so they can be imported into ClearCase or ClearCase LT elements and versions. The source data can range from a single file to an entire directory tree.
During the export stage, you invoke clearexport_rcs in the area where the RCS files reside. clearexport_rcs creates a datafile (by default, named cvt_data), and places in it descriptions of elements, branches, and versions. clearexport_rcs follows symbolic links it encounters during the export stage.
In the import stage, you invoke clearimport on the datafile to import information into the new VOB.
clearexport_rcs ignores most information in RCS files that is not related to version-tree structure. clearexport_rcs converts each RCS symbol, which names a revision or branch, into the appropriate construct: version label or branch. You can specify a translation file to control naming, enforcing consistency over multiple invocations of clearexport_rcs. You can use the -S and -V options to preserve RCS state attributes and RCS revision numbers as attributes of the corresponding ClearCase or ClearCase LT versions.
clearexport_rcs and clearimport use magic files to determine which element type to use for each element clearimport creates. For more information on magic files and file typing, see the cc.magic reference page.
NOTE: You cannot run clearexport_rcs on UNIX and then run clearimport on Windows to import the data, or vice-versa. However, you can transfer data in either direction between UNIX and Windows by mounting the UNIX VOB or file-system on the Windows machine and running both clearexport_rcs and clearimport on the Windows machine.
clearexport_rcs works directly with the structured RCS files. It does not process the working files created with co and co -l commands. Be sure to check in working files with the ci command before running the exporter. clearexport_rcs issues warning messages when it encounters checked-out files, but it still processes them.
clearexport_rcs ignores all RCS locks.
If RCS files are stored in RCS (or rcs; case is not important) subdirectories, clearexport_rcs collapses the subdirectory level in the export process. For example, RCS file ./proj/RCS/main.c,v becomes element ./proj/main.c.
During import, clearimport invokes a shell to extract data from the datafile. clearimport can handle some, but not all, characters that are special to shells. Import fails for any file name that includes any of these characters:
` ' " <Tab> [ ] ? * %
Succeeds | Fails |
---|---|
foo&bar |
foo[bar |
$MY_LIB |
yellow`sunset |
file name |
file*name |
Before running clearexport_rcs, rename any file whose name contains these characters.
NOTE: If you specify datafile-pname or source-name and any of the names include spaces, you must escape the space characters (UNIX):
% clearexport_rcs src\ files
or enclose the name in double quotes (Windows):
> clearexport_rcs "src files"
An RCS symbol is a mnemonic name for a particular revision or branch of an RCS file. clearexport_rcs translates the symbols to version labels and branch names (more precisely, to names of label types and branch types).
Translation to version labels - Suppose an RCS symbol, RLS_1.3, names a revision, 3.5. clearexport_rcs places a description of label type RLS_1.3 in the datafile, and clearimport imports that label type and assigns a label of that type to the version created from the RCS revision.
Translation to branch names - Suppose an RCS symbol, rls_1.3_fixes, names a branch 3.5.1. clearexport_rcs outputs a description of branch type rls_1.3_fixes, and clearimport creates a branch of that type at the ClearCase or ClearCase LT version created from RCS revision 3.5.
Because there is no concept of a subbranch of the main branch, clearexport_rcs does not process single-digit symbols that name RCS branches. If an RCS symbol includes characters that are not valid in names of label types or branch types, clearexport_rcs replaces the offending name. For example, the RCS symbol C++ can be renamed to "C..".
A label type cannot have the same name as a branch type within the same VOB. If the same RCS symbol names both a revision and a branch-not necessarily in the same RCS file-clearexport_rcs renames one of them. For example, after exporting a symbol FX354, which names a branch, it may encounter the same symbol as the name of a revision in another RCS file. In this case, it creates label type FX354_1.
This renaming of RCS symbols can introduce inconsistencies over multiple runs of clearexport_rcs. The same symbol may be renamed during processing of some RCS files, but not chang during processing of other files. You can enforce consistency by using the same translation file in multiple invocations of clearexport_rcs. If you name such a file, using the -T option, clearexport_rcs uses it as follows:
To look up each RCS symbol to see how to translate it to a label type or branch type. If a match is found, the symbol is translated the same way.
To record each translation of a new RCS symbol for use in future lookups.
The first time you use clearexport_rcs, use -T to create a new translation file. On subsequent invocations of clearexport_rcs, use -T again, specifying the same translation file for consistent name translation.
The translation file consists of one or more lines in the following form:
{ label | branch } old-name new-name
For example, to rename the branch type pre_import_work to post_import_work and the label BL1.7 to IMPORT_BASE, the translation file contains the lines:
branch pre_import_work post_import_work
label BL1.7 IMPORT_BASE
No blank lines are allowed in the file.
When clearexport_rcs encounters a file or directory that cannot be exported (for example, a file with format problems, or a broken symbolic link), it prints an error and continues. After creating the data file, the command prints a summary of the files and directories that could not be exported.
HANDLING OF DIRECTORY ARGUMENTS. Default: If you specify a directory as a source-name argument: (1) clearexport_rcs Processes the files in that directory but ignores the contents of the subdirectories; (2) clearimport creates a directory element for source-name and for each of its subdirectories.
SELECTIVE CONVERSION OF FILES. Default: clearexport_rcs processes all RCS revisions it finds.
|
|
|
|
|
|
date | := | day-of-week | long-date |
time | := | h[h]:m[m][:s[s]] [UTC [ [ + | - ]h[h][:m[m] ] ] ] |
day-of-week | := | today |yesterday |Sunday | ... |Saturday |Sun | ... |Sat |
long-date | := | d[d]-month[-[yy]yy] |
month | := | January |... |December |Jan |... |Dec |
PRESERVATION OF RCS INFORMATION AS ATTRIBUTES. Default: clearexport_rcs does not attach attributes to versions exported from RCS revisions.
DIRECTORY FOR TEMPORARY FILES. Default on UNIX systems: the value of P_tmpdir (set in the stdio.h system include file; you can override this value by setting the TMPDIR environment variable). Default on Windows systems: the value of the TMP environment variable.
HANDLING OF BRANCHES AND LABELS. Default: As described in the section HANDLING OF RCS SYMBOLS, clearexport_rcs may rename a branch or label type to avoid naming conflicts.
STORAGE LOCATION OF DATAFILE. Default: clearexport_rcs creates datafile cvt_data in the current working directory.
SPECIFYING FILES TO BE EXPORTED. Default: clearexport_rcs processes the current working directory (equivalent to specifying "." as the source-name argument). If you specify a directory as a source-name argument: (1) clearexport_rcs processes the files in that directory but ignores the contents of the subdirectories; (2) clearimport creates a directory element for source-name and for each of its subdirectories (except one named RCS or rcs).
|
|
Create a datafile for a single RCS file.
clearexport_rcs myprogram.c,v
Process three RCS files in the current working directory and store the datafile in file cvt_include.
clearexport_rcs -o cvt_include bgr1.h,v bgr2.h,v bgr3.h,v
clearexport_*, clearimport, events_ccase, relocate, rcs(1), rsh(1) or remsh(1), sccs(1)
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |