Importing PVCS data

This example demonstrates the use of command-line tools to import data from PVCS to a newly created VOB. The PVCS tree is located at C:\libpub, on a host where the empty VOB has been activated, at \libpub.

Create the data file.
1. Go to the source data. Change to the directory of the existing PVCS source tree:
  c:\> cd libpub
2. Run the export utility. Use clearexport_pvcs to create the data file and place descriptions of PVCS files in it:
  c:\libpub> clearexport_pvcs
  Exporting element ".\makefile" ... Extracting element history ... . Completed. Exporting element ... Creating element ... Element ".\makefile" completed. . . Element ".\lineseq.c" completed. Creating datafile .\cvt_data ...
  The data file, cvt_data, is created in the current directory.
Import the data file.
1. Use any view. clearimport ignores the config spec. Using a dynamic view improves the performance of the import operation.
2. Go to the target VOB. Change to the root directory of /vobs/libpub:
  cd /vobs/libpub
3. Run clearimport. Run clearimport on the datafile, cvt_data, to populate \libpub:
  z:\vob_libpub> clearimport c:\libpub\cvt_data
  Converting files from c:\libpub to . Created element ".\.\makefile" (type "text_file"). Changed protection on ".\.\makefile". Making version of .\.\makefile Checked out ".\.\makefile" from version "\main\0". Comment for all listed objects: Checked in ".\.\makefile" version "\main\1". . .
  There is no need to check out or check in the VOB’s root directory element; this is handled automatically. If problems cause clearimport to terminate prematurely, you can fix the problems and run clearimport again.