On Tue, Jul 03, 2001 at 03:39:03PM -0500, david d zuhn wrote:

VCP-0.1 is out on CPAN or you can sync from public.perforce.com:1666 //perforce/revml/...@vcp_00_1 into your local build directory and do the standard "perl Makefile.PL && make && make test && make install" bit (it'll take a while before it gets relayed to your local CPAN host). It's also at http://slaysys.com/src/VCP-0.1.tar.gz if all else fails.

The only change is that p4: destinations now allow p4:/foo syntax. Here's the docs (which also now talk about change number aggregation):

vcp <source> p4[:<dest>]

where <dest> is a filespec to a directory in the perforce repository or on the local client of the directory tree to use when importing files (this is known as the "rev root", for lack of a better term).

The <dest> spec is run through the `p4 where` command to get an absolute path on the local filesystem. `p4 where` must generate exactly one line of output, and the line is parsed to strip off the depot and client filespecs, including file and directory names containing spaces (directory names containing trailing spaces are not handled correctly!).

See `p4 help where` and the Perforce User's Guide for details on how to specify the <dest>, but here's an overview (do check the Perforce User's Guide to see if your version of `p4 where` behaves differently):

* any //depot/, //client/, or absolute or relative local filesystem spec can be supplied for <dest> (local specs should not begin with "//" even if the local OS would be Ok with it).

* No need to type "/..." at the end of <dest>, VCP::Dest::p4 adds it if it's missing.

* Relative specs (or a missing <dest>) are taken (by p4 where) to be relative to the current working directory.

* You cannot put directory names like "./" or "../" in the middle of any spec, only at the beginning of a relative local filesystem spec.

VCP::Dest::p4 does change number aggregation, see the rev_cmp_sub entry in the VCP::Dest manpage for the order in which revisions are sorted. Once sorted, a change is submitted whenever the change number (if present) changes, the comment (if present) changes, or a new rev of a file with the same name as a revision that's pending. THIS IS EXPERIMENTAL, PLEASE DOUBLE CHECK EVERYTHING!