Migrating from source repository to SVN

Question

I had a local Source Depot repository for version control since my days at Microsoft. Recently, I want to switch to SVN and take the change history with me, but there seems to be no script to switch to SVN.

Since there are quite a few Microsofties that hang out here, I thought I would try here. I am mostly looking for a lightweight migration script that will take care of me.

The prohibition that any other advice welcomes me. FYI, Source Depot is based on Perforce, and without any success I tried to port the tools port.

Answer 1

Does Source Depot have a command line similar to Perforce?

About a year ago, I moved my SCC home repository from Perforce to SVN in a few steps using a Python script. While I no longer have a script, it was pretty simple and was written one afternoon.

Basically, the script started from the very first list of changes and went through everything. It will synchronize with each change list and split the files into edit / add / branch lists. Then these files will be copied to the SVN path and updated / added / forked using the appropriate commands. They will then be used with a comment from the original change list.

This gave me a full SVN mirror of my Perforce warehouse with all the stories / comments and affiliate information. I had only one user (me!), But it would not be difficult to support multiple uses.

I even played around with the idea that the script would change the system clock so that the history dates were correct, but it was not worth it. For me, the most important thing was the history and information about the branch / tags.

Answer 2

My company had a contractor who visited us for an information session some time ago about transferring the entire source history and version from MKS to SVN. It turns out that it’s actually very difficult to keep the version history unchanged during the migration process, because everyone has their own methods for storing this history. What I removed from this visit was that there are some expensive third-party tools that will perform migrations, but they are hard to find and really not so good.

We decided that for most projects we would bite the bullet and simply create new version control projects with an existing source, losing version history for new software and saving old backups to disk.

Of course, our situations are slightly different in that our basic versions are not in the same format (my MKS, your SD). But, I do not believe that it will be easy to find a magic script to convert it. I could be wrong, but this is what I chose from the meeting that we had, anyway.

Answer 3

I may not understand your problem, but what prevents you from doing a full code check from Source Depot and then checking it for Subversion?

If you also do not want to import any user / group controls that have been configured, then checkout / registration would not have fully completed this.