Converts PVCS files to elements
Product | Command Type |
---|---|
ClearCase | command |
ClearCase LT | command |
Platform |
---|
UNIX |
Windows |
The clearexport_pvcs command processes PVCS files so they can be imported into elements and versions. The source data for export can range from a single file to an entire directory tree.
During the export stage, you invoke clearexport_pvcs in the directory where the PVCS files reside. clearexport_pvcs creates a datafile (by default, named cvt_data) and places in it descriptions of elements, branches, and versions.
In the import stage, you invoke clearimport on the datafile to import information into the new VOB.
clearexport_pvcs ignores most information in PVCS files that is not related to version-tree structure. clearexport_pvcs converts each PVCS label, 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_pvcs.) You can use the -V option to preserve PVCS revision numbers as attributes of the corresponding ClearCase or ClearCase LT versions.
clearexport_pvcs 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_pvcs 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 your Windows machine and running both clearexport_pvcs and clearimport on the Windows machine.
clearexport_pvcs works directly with PVCS files. It does not process the workfiles created with the get and get -l commands. Be sure to check in workfiles with the put command before running the exporter.
clearexport_pvcs issues warning messages when it encounters checked-out files, but it still processes them. clearexport_pvcs ignores all PVCS locks.
If PVCS files are stored in VCS (or vcs; case is not important) subdirectories, clearexport_pvcs collapses the subdirectory level. For example, PVCS file ./proj/VCS/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_pvcs, 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_pvcs src\ files
or enclose the name in double quotes (Windows):
> clearexport_pvcs "src files"
A PVCS symbol is a mnemonic name for a particular revision or branch of a PVCS file. clearexport_pvcs translates the symbols to version labels and branch names (more precisely, to names of label types and branch types).
Translation to version labels - Suppose a PVCS symbol, RLS_1.3, names a revision, 3.5. clearexport_pvcs 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 appropriate version.
Translation to branch names - Suppose a PVCS symbol, rls_1.3_fixes, names a branch, 3.5.1. clearexport_pvcs outputs information about branch type rls_1.3_fixes, and clearimport creates a branch of that type at the appropriate version.
Because there is no concept of a subbranch of the main branch, clearexport_pvcs does not process single-digit symbols that name PVCS branches. If a PVCS symbol includes characters that are not valid in names of label types or branch types, clearexport_pvcs replaces the offending name. For example, the PVCS symbol C++ may be renamed to "C..".
A label type cannot have the same name as a branch type within the same VOB. If the same PVCS symbol names both a revision and a branch-not necessarily in the same PVCS file-clearexport_pvcs 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 PVCS file. In this case, it creates label type FX354_1.
Renaming PVCS symbols can introduce inconsistencies over multiple runs of clearexport_pvcs. The same symbol may be renamed during processing of some PVCS files, but not chang during processing of other files. You can enforce consistency by using the same translation file in multiple invocations of clearexport_pvcs. If you name such a file, using the -T option, clearexport_pvcs uses it as follows:
To look up each PVCS 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 PVCS symbol, for use in future lookups.
The first time you use clearexport_pvcs, use -T to create a new translation file. On subsequent invocations of clearexport_pvcs, 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_pvcs 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, it 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_pvcs 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_pvcs processes all files it encounters.
|
|
|
|
|
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 PVCS INFORMATION AS ATTRIBUTES. Default: clearexport_pvcs does not attach attributes to versions exported from PVCS 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.
TRANSLATION OF BRANCHES AND LABELS. Default: As described in the section HANDLING OF PVCS SYMBOLS, clearexport_pvcs may rename a branch or label type to avoid naming conflicts.
STORAGE LOCATION OF DATAFILE. Default: clearexport_pvcs creates datafile cvt_data in the current working directory.
SPECIFYING FILES TO BE EXPORTED. Default: clearexport_pvcs processes the current working directory (equivalent to specifying "."as the source-name argument). clearimport creates an element in the new VOB for each element in the current working directory. clearimport creates a directory element in the new VOB for each subdirectory of the current working directory (except one named PVCS or pvcs).
|
---|
|
Create entries in the datafile for the entire tree under directory element src, exporting important versions created before 1999 and all versions created since the beginning of 1999.
clearexport_pvcs -r -I 1-Jan-1999 src
Create entries in the datafile for the elements in the current working directory, but not in any subdirectories; store the datafile in a file named newcvt.
clearexport_pvcs -o newcvt .
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. |