[p4] CVS <--> Perforce replication
barries at slaysys.com
Wed Jun 20 20:22:22 PDT 2001
On Wed, Jun 20, 2001 at 02:09:45PM -0400, Geoff Talvola wrote:
> Are there any tools available that will let you keep a Perforce depot and a
> CVS repository in sync?
VCP is designed to do this, it's in beta now. The biggest drawbacks are
that it doesn't yet attempt to remember what's been transferred (either
as state stored anywhere or by examining the repositories), so you need
to use tags/labels/change numbers, and that it doesn't know from
Easiest way to get up and running with VCP is to do (on a Unix box, NT
not supported yet):
perl -MCPAN -e 'install "VCP"'
as root. The advantage to using CPAN to install it is that it will also
install all the prerequisite modules automatically.
Once all the prereqs are installed, it's easy to sync VCP to the
perforce public depot to get bugfixes, etc.
The mailing list is revml at perforce.com, see:
(RevML is an XML-derived markup langauge that can be used to transfer
sets of revisions en masse or as deltas, VCP can read/write RevML in
addition to p4 and cvs repositories).
> I'm basically thinking of a review daemon-type
> thing that will poll periodically and automatically check in changes to CVS
> into Perforce and vice-versa.
Hmmmm, bidirectional replication is an interesting challenge.
> It doesn't need to handle branching and if
> there are conflicting changes in Perforce and CVS it's OK if it just gives
> up and sends an error email.
> It should also ideally group CVS checkins
> into changelists.
VCP does aggregate runs of CVS checkins in to changes.
More information about the perforce-user