All of the sources, destination, and filters can now dump config file sections and bin/vcp has grown the option --output-config-file=foo.bar to write a .vcp file. Here's an all-too-siple

You can write a .vcp file from any source: command line parms, an existing config file or the UI. This can be useful to see how VCP parsed your input, or to add commented-out options to the .vcp file.

There need to be comments added to each of the options, etc, and we should add a "don't convert" command line option, but the required functionality should all there.

In addition to this option, the UI will soon ask if the user wants to write a config file as well.

This command:

$ vcp --output-config-file=out.vcp cvs2p4.vcp

created this file:

Source: cvs:t/cvsroot_0:foo/ #--bootstrap=??? #--cd=??? #--continue #--d=??? #--db-dir=??? #--k=??? #--kb #--r=??? --repo-id=cvs:test_repository --rev-root=foo #--use-cvs

Dest: p4:localhost:27813://depot/... --change-branch-rev-1 --db-dir=$state_location --delete-p4d-dir --init-p4d --repo-id=p4:test_repository #--run-p4d

Map: # Pattern Replacement # ============ =========== (...)<> main/$1 (...)<(...)> $2/$1

after reading this file:

Options: -d

Source: cvs:t/cvsroot_0:foo/ --repo-id=cvs:test_repository

Destination: p4:tmp/p4out://depot/... --init-p4d --delete-p4d-dir --db-dir=$state_location --repo-id=p4:test_repository --change-branch-rev-1

Map: (...)<> main/$1 # Match files on main branch (only) (...)<(...)> $2/$1 # Match files on branches

- Barrie