Copyright: Copyright(c) 1992-1997, StarBase Corporation
Citation: Copyright(c) 1992-1997, StarBase Corporation. All rights reserved.


Overview
 PVCS Import Overview

The PVCS Import tool is a stand-alone executable, pvcsimp.exe. It locates a PVCS installation by looking for PVCS’s islv.ini file in your Windows directory (for example, c:\windows\islv.ini). It displays a list of projects from the .ini file and allows you to import projects into Versions. Importing PVCS projects does not alter or delete those PVCS projects. The import process only copies information from them into Versions databases and vaults, creating Versions projects.

PVCS Import Features:

•	Reads the PVCS project information and allows you to select PVCS projects for import.

•	Maps PVCS folders to Versions subprojects.

•	Imports all or only the last revision of the main trunk of all archives.

•	Imports all check-in information such as author, (original) date of check-in, version comment, labels, etc.

•	Reports all actions performed during the import online in the Versions PVCS Import dialog and logs the actions in a log file as well.

•	If you cancel the import after it starts, the partially constructed project is deleted. So are all the vault files and databases. The directory structure is left unchanged. The original PVCS files are left undeleted.

Limitations and differences:

•	Imports projects from the PVCS 5.2’s 32-bit edition only.

•	Does not support multiple references to a vault (archive) file. When the Project Folder and other user-created PVCS folders contain the same file, that file is imported as a part of only one of those user-created folders.

•	Does not support PVCS branches. Only the main trunk is imported. Ignored branches are not reported in the log file.

•	Does not import promotion definitions or private folders because Versions does not support them.

•	PVCS uses revision names such as “1.1”, while Versions uses version numbers, such as 1, 2, and 3. The revision numbers of the PVCS main trunk are mapped to Versions version numbers.

 Related Topics


Import a project from PVCS
 Import projects from PVCS

You can import projects (one at a time) from PVCS 5.2 to Versions. Be sure to check in all changed working files prior to performing the import so that no work is lost.

To import projects from PVCS:

1.	Select PVCS Import to run pvcsimp.exe.
If PVCS Import finds a PVCS installation, the Versions PVCS Import dialog opens.

2.	Select a project to import from the Projects list box.

3.	To see details about the PVCS project, click Project Detail.
The Log Output box displays information about the selected project, such as its name, configuration file, project descriptor root, archive directory, working directory, folder names, and filenames.

4.	Click Import... to specify the information Versions needs to create a project.
The Project Import Parameters dialog opens.

5.	Type a name for this project in the Project Name text box (or use its PVCS name which is the default).

6.	Type the pathname for the working directory for the project root.
Or,
Click Browse... to locate one.

7.	Type the pathname for the file that will store the Versions project database file (.stp).
The directory that stores the project database file will also store the project vault, the equivalent of PVCS’s archive directory.
The revisions (or versions) of files from the imported project will go into the project vault. Versions uses the name of the project database file (but this time with the extension .vlt) as the name of the vault directory. Let Versions control these files! Do not delete them or modify them in any way.

8.	Type the name of a person who will be an administrator for the project in the First User text box.
An administrator can set project properties, assign users, etc. Authors of files in the project also become administrators as part of the import process.

9.	Select Import All Revisions (main trunk) or the Import Latest Revision Only option button to indicate how many versions of each file to import.

10.	Select the Compress check box to compress the vault files of the imported files or leave it cleared to avoid compression.

11.	Use the default log file name to record the actions performed during the import process.
Or,
Type the pathname for a log file.
Or,
Click Browse... to locate one.

12.	Click Import.
A progress dialog displays a progress meter. A Cancel button in the progress dialog allows you to cancel the import.

13.	After the import, the Versions PVCS Import dialog reappears.
Repeat steps 2 through 11 to import another project or click Done.

 Related Topics


 Inspect the imported files

After you import a project from PVCS 5.2 to Versions, you will want to look at the results.

To inspect the imported files:

1.	Run Versions.

2.	Click Open Project [image] and locate the .stp file for the imported project.
The project window opens.

3.	Click All Descendants, the rightmost of the three scope buttons, to see the contents of all the subprojects.
You see the name of each file, its author, description, subproject, path, etc.

4.	Use Versions Help for more details.

 Related Topics


 Check out the imported files

After you import a project from PVCS 5.2 to Versions, it is a good idea to check out all of the files you will be using.

To check out all the imported files:

1.	Run Versions.

2.	Click Open Project [image] and locate the .stp file for the imported project.
The project window opens.

3.	Click All Descendants, the rightmost of the three scope buttons, to see the contents of all the subprojects.
You see the name of each file, its author, description, subproject, path, etc.

4.	Select Files · Select All... from the menu bar.

5.	Select Files · Check Out... from the menu bar. Select the Force Check Out check box, and click OK.

 Related Topics


Specify project properties (after importing projects with PVCSImport)
 Specify project properties

After you import a project from PVCS 5.2 to Versions, you will want to set properties for it in Versions.

To set project properties:

1.	Run Versions.

2.	Open the imported project.

3.	Select Project · Properties... from the menu bar.
The Project Properties dialog opens.

4.	Use Versions Help for more details.

 Related Topics


 Versions PVCS Import

You can import projects (one at a time) from PVCS 5.2 to Versions. Be sure to check in all changed working files prior to performing the import.

Projects
Displays your PVCS projects (with the exception of the Master Project which has no meaning in Versions).
Select a project to import.

Log output
Displays information about the PVCS .ini file, such as the project’s root directory, private project’s root directory, and the PVCS version number. When you click Project Detail, it displays information about the selected project, such as its name, configuration file, project descriptor root, archive directory, working directory, folder names, and filenames.

Project Detail
Click to display details about the selected project.

Import...
Click to specify information needed by Versions to import the selected project.

Done
Click to exit PVCS Import.


 Project Import Parameters

To import a project, you must specify a project name, its working directory, and the name of a project database file.

New Versions project

Project name
Type the name for this project in Versions.
The default is the project name used in PVCS.

Working directory
Type the pathname for the working directory for the project root.

Browse...
Click to browse for the working directory.

Project file
Type the pathname for the file that will store the project database. The extension for this file is .stp.

Browse...
Click to browse for the directory that will store the project file.

First user
Type the name of a person who will be an administrator for the project. Use the name that person would use to log on to the project.

Import Parameters
Select the appropriate option button.

Import all revisions (main trunk)	Imports all the revisions stored by PVCS 5.2 for each file in the project.

Import latest revision only	Imports only the latest revision stored by PVCS 5.2 for each file in the project.

Compress
Select to compress the vault files of the imported files. Leave it cleared to avoid compression.

Log file
Type the pathname for a file that will store the log for the import process.
By default, the pathname for this file is the same as the project file’s pathname, except that the extension is .log.

Browse...
Click to browse for the directory that will store the log file.

Import
Click to import the project.


 Save As

Use this dialog to create a project database file (.stp) or an import log file (.log).

File name
Type the pathname for the file you want to create.

Save file as type
Preset to *.stp or *.log, depending on the type of file to be created.

Folders/Directories
Select a Windows 95 folder or a directory to store the file.

Drives
Select an appropriate drive.

Network
Click to map a network drive.


 Project Working Directory

Use this dialog to select a working directory for the project root.

Folders/Directories
Select a Windows 95 folder or a directory.

Drives
Select an appropriate drive.

Network
Click to map a network drive.


 workstation database

Stwork20a.db is the workstation database file. The database contains information about what versions of files are in your working directories and so forth. For example, Versions uses it to determine what needs to be checked in or out.


 milestone

An event in the life cycle of a product chosen to represent a significant step in progress, for example, the alpha, beta, or final release of a product. In Versions a milestone designates a single set of permanent versions for the files in a project. Each version in the milestone has the same label. When project security is enabled, only an administrator can designate a milestone. Milestones cannot be designated at the subproject level.