23 messages in com.perforce.revml[revml] Re: [p4] cvs to perforce usin...
FromSent OnAttachments
barries02 Jul 2001 08:36 
david d zuhn03 Jul 2001 08:48 
barries03 Jul 2001 09:38 
david d zuhn03 Jul 2001 11:43 
barries03 Jul 2001 13:22 
barries03 Jul 2001 21:56 
david d zuhn05 Jul 2001 09:13 
barries05 Jul 2001 10:58 
david d zuhn05 Jul 2001 11:17 
barries05 Jul 2001 11:25 
david d zuhn05 Jul 2001 11:44 
barries05 Jul 2001 12:20 
barries16 Jul 2001 11:51 
david d zuhn16 Jul 2001 11:51 
david d zuhn18 Jul 2001 12:04 
barries18 Jul 2001 12:40 
david d zuhn18 Jul 2001 12:56 
barries18 Jul 2001 14:09 
ste...@vance.com19 Jul 2001 07:37 
barries19 Jul 2001 07:42 
david d zuhn19 Jul 2001 11:19 
barries19 Jul 2001 11:25 
barries19 Jul 2001 13:54 
Subject:[revml] Re: [p4] cvs to perforce using VCP package......
From:barries (barr@slaysys.com)
Date:07/03/2001 09:38:29 AM
List:com.perforce.revml

On Tue, Jul 03, 2001 at 10:48:32AM -0500, david d zuhn wrote:

At 11:36 AM 7/2/2001 -0400, you wrote:

On Tue, Jun 26, 2001 at 02:18:03PM -0700, Usha Rajesh wrote:

Has anyone done a cvs to perforce migration using the VCP pack available from the CPAN site ? if so, could you help me out in doing a migration ? I am getting some kind of error in the process in which I do the migration through revml.

Sorry for the delay, was on vacation for a few days. The support list is rev@perforce.com (note the Reply-To header on this message), and I'll be glad to help you. Can you post some details?

Well, I'll take you up on this.

First of all, from reading sources & such, I think to do a CVS to Perforce source movement, I need to do this via revml, since the CVS source side wants to be in the CVS sandbox, and the P4 destination side wants to be in the P4 client workspace. Is this actually the case, or am I misreading things?

You can do cvs->p4 directly, it chdirs before each invocation of the cvs and p4 utilities (there's a VCP::Plugin::command_dir() method that sets the working dir for the default command used by a plugin). What errors do you get trying this?

So I'm using RevML as the intermediate, and that seems to be working fine for me, except that I'm unable to specify a target path within the Perforce depot space:

$ vcp revml:kernel-sys.ml p4://depot/bravos/sys vcp: No spec '//depot/bravos/sys' allowed for destination class p4: at /tools/lib/perl5/site_perl/5.6.1/VCP/Dest/p4.pm line 81

VCP::Dest::p4 is supposed to accept a destination filespec and use it as the rev_root, ignoring any trailing "..." wildcard. I'll work on that over the July 4th holiday here. Thanks for finding that, rerooting transferred trees is a must-have. Time to add it to the test suite, too (which will take some time, verifying that is going to be a pain, I think).

- Barrie