tags:

views:

490

answers:

3

I have started work for a company which is in the process of in-housing their main application previously managed by an agency.

The codebase is currently stored in a Perforce repository. What I would like to do is migrate this codebase, complete with revision history, to a newly built Subvesrion server.

Is anyone aware of any scripts or tools that will help me acomplish this?

A: 

Try googling for it

http://www.google.com/search?hl=en&q=perforce+to+subversion+migration&aq=f&oq=&aqi=

artemb
http://www.lmgtfy.com/?q=perforce+to+subversion+migration `:)`
sbi
Have you tried googling for it? The results you get back do not really answer the question.
Simon Nickerson
Oh really? Here is a "p42svn" perl script for exactly migrating from perforce to subversion:http://svn.haxx.se/dev/archive-2003-08/0133.shtmlThis link is on the first page of google results
artemb
@artemb: The links on that page are stale. If you don't know the answer, what's the point in saying "try googling"?
Simon Nickerson
I have actually been working with the p42svn script for a while. Ultimately the roadblock I hit (after much faffing about) was that the version of Perforce I am attempting to read from is too old and the P4Perl API returns unexpected data when the script attempts to diff files. I haven't tried too hard, but I suspect my Perl (or time) is insufficient to fix.Unfortunately Googling has yet to turn up any alternatives. Not even Binging or Yahooing helped ;-)
Jamie
If the code is really that old do you really need all the branches? You could just take the tip and save the revision hisrtory for some context. If you do need all the branches etc. than maybe you could update depot to the latest P4 and then convert over to SVN??? Just some thoughts...
stephenmm
A: 

http://stackoverflow.com/questions/395702/migrating-from-svn-to-perforce-tips-experience

I used a modified version of this script for our migration. Biggest problem I had was the shear amount of disk space required to have a working copy for every branch on the migration machine.

My version had a few fixes relating to Windows use and a few bug fixes for cases I hit during our migration. Contact me if you want my modified version of this script.

Paul Ruane
A: 

Try: http://p42svn.tigris.org/

But I agree with the earlier comments - I've gone the other direction, moving projects from SVN to Perforce because SVN could not cut it when it came to merging. Maybe it's gotten much better since 1.5.4, but while P4 has it's oddities and complexities - it's a more robust solution for large projects that do branching.

Rob Neely