vcp - Copy versions of files between repositories and/or RevML
vcp [vcp_opts] <source> <dest>
vcp help [topic]
vcp html <destination dir>
vcp
('version copy') copies versions of files from one repository to another,
translating as much metadata as possible along the way. This allows you to
copy and translate files and their histories between revision storage systems.
Supported source and destination types are cvs:
, p4:
, and revml:
.
The general syntax of the vcp command line is:
vcp [<vcp options>] <source> <dest>
The three portions of the command line are:
<vcp options>
vcp
command, like
-d
for debugging or -h
for help. There are very few global options,
these are covered below. Note that they must come before the
<source>
specification.
<source>
<dest>
The <source>
and <dest>
specifications specify a
repository and provide any options needed for accessing that repository.
These spefications may be a simple filename for reading or writing RevML
files (if the requisite XML handling modules are installed). or a full
repository specification like cvs:/home/cvs/root:module
or
p4:user:password@server:port://depot/dir
.
When using the long form to access a repository, <source>
and
<dest>
specification have several fields delimited by :
and @
, and may have trailing command line options. The full (rarely
used) syntax is:
scheme:user(view):password@repository:filespec [<options>]
where
scheme:
p4:
, cvs:
, revml:
).
user
, view
, and password
cvs
does not use view
. For p4
, view
is the client
setting (equibalent to setting P4CLIENT
or using p4
's -c
option).
repository
filespec
<options>
cvs
, p4
, etc).
Most of these fields are omitted in practice, only the scheme
field is
required, though (in most cases) the repository
field is also needed unless
you set the appropriate environment variables (CVSROOT
, P4PORT
, etc).
The a bit confusing, here are some examples specs:
cvs:server:/foo p4:user@server://depot/foo/... p4:user:password@public.perforce.com:1666://depot/foo/...
Options and formats for of individual schemes can be found in the relevant help topics, for instance:
vcp help source::cvs
See vcp help
for a list of source and destination topics.
When reading and writing RevML files, a simple filename will do (although the long form may also be used). The special value "-" means to read/write stdin and stdout when used as a source or destination name, respectively. "-" is assumed if a specification is not provided, so these invocations all accomplish the same thing, reading and writing RevML:
vcp vcp - vcp revml:- vcp revml: vcp - - vcp - revml:- vcp - revml: vcp revml:- revml:- vcp revml: revml:
vcp
Options
All general options to vcp must precede the <source>
.
Scheme-specific options must be placed immediately after the
<source>
or <dest>
spec and before the next one.
--debug <spec>, -d <spec>
Source::revml
or a perl5 regular expression to match module
names. Debug specs are not case insensitively.
The most general, show-me-everything debug option is:
-d ".*"
The quotations are needed to slip the ".*" past most command shells.
Any debug specs that don't match anything during a run are printed out when vcp exits in order to help identify mispelled patterns. vcp will also list all of the internal names that didn't match during a run to give clues as to what specs might be useful.
The special name 'what' is guaranteed to not match anything, so you can do
vcp -d what ...
to see the list of names that might be useful for the arguments '...' .
You may use multiple
-d
options or provide a comma separated list to enable debugging
within that module. Do not start a pattern with a "-".
Debugging messages are emitted to stderr. See /VCPDEBUG for how to specify debug options in the environment.
--help, -h, -?
vcp help
.
(See also Generating HTML Documentation, below).
There is a slightly different command line format for requesting help:
vcp help [<topic>]
where <topic>
is the optional name of a topic. vcp help
without
a <
topic>
prints out a list of topics, and vcp help vcp
emits this page.
All help documents are also available as Unix man
pages and using the
perldoc
command, although the names are slightly different:
with vcp via perldoc ================ =========== vcp help vcp perldoc vcp vcp help source::cvs perldoc VCP::Source::cvs vcp help source::cvs perldoc VCP::Dest::p4
vcp help
is case insensitive, perldoc
and man
may or may not be
depending on your filesystem. The man
commands look just like the example
perldoc
commands except for the command name. Both have the advantage that
they use your system's configured pager if possible.
VCPDEBUG
There is also one environment variable that is used to enable
command line debugging. The VCPDEBUG variable acts just like a leading
-d=$VCPDEBUG
was present on the command line.
VCPDEBUG=main,p4
(see "--debug <spec>, -d <spec>" for more info). This is useful when VCP is embedded in another application, like a makefile or a test suite.
All of the help pages in vcp
can be built in to an HTML tree with the
command:
vcp html <dest_dir>
The index file will be <dest_dir>/index.html
.
VCP::Process, VCP::Newlines, VCP::Source::p4, VCP::Dest::p4,
VCP::Source::cvs, VCP::Dest::cvs, VCP::Source::revml,
VCP::Dest::revml, VCP::Newlines. All are also available using vcp
help
.
Barrie Slaymaker <barries@slaysys.com>
Copyright (c) 2000, 2001, 2002 Perforce Software, Inc. All rights reserved.
See VCP::License (vcp help license
) for the terms of use.