views:

36

answers:

2

I have a subversion repository located on our school servers from a project my friends and I worked on the past semester. We want to take the project and polish it and make it more of a portfolio item and I'm not quite sure that the repo will stay intact on the school servers (they usually wipe it after a few semesters). I don't have access to dump the repo, although I've sent an email to see if I can get one - which would be the best solution.

I tried svnsync but the school server doesn't support the replay command (probably turned off), so that won't work for me.

Now, theoretically, wouldn't it be possible to (manually or programmatically) checkout each revision of the repository and check it in to a new repository on our own server? I think it would work - there's only 3 of us, and there's no working copy conflicts that we'd have to worry about, just want a copy of all the history in the repo in case we need to go back and look at it.

That being said, before I go and reinvent a wheel by writing a script to do it - does something like this already exist? I have to figure there's already a tool to do it, or that someone has wrote a script to do it.

A: 
balpha
Again, not looking to switch at the moment - I'm comfortable with subversion at the moment ;) Although I might take a look at it. I think I may have found a solution but it's late so I'll probably give it a whirl tomorrow.
Corazu
A: 

You didnt specify how many revisions you have approximately in your project. And a script based check out for each revision is possible. But it is not realistic, because of all the ".svn" folders created for each folder. Because of them, you

  1. Would either need another script do a recursive delete of these files, before another script can check it in.
  2. Or, for each revision do an svn export, and then write another script that will check it in.

As you can see its not feasible. And I do not know of a script to do this.

You can however do a number of exports from the repo, each one of the most important commits, and then add them to your new repository. If there are less number of revisions then it should be easier.

omermuhammed
Given enough time to export all revisions, why wouldn't it be possible?
sbi
There's only 162 revisions and not all that many folders..I don't think it would take that long or be that difficult.
Corazu