tags:

views:

1603

answers:

3

Currently I have a root-level repository set up for each project, like so:

Project1
Project2
Project3
Project5
Project5

I'd like to reorganise this so that rather than a repository for each individual project, I just have one for each logical grouping, and then the projects would just be folders within those 'group repositories', e.g:

WebSites
    Project1
    Project2
DesktopApps
    Project3
Libraries
    Project4
    Project5

Is this at all possible while retaining the history of the existing repositories? I've looked around quite a bit but all I can find is stuff on moving folders about within the same repository, and moving folders out of a repository into a new repository.

It's only for personal stuff anyway, so it's not the end of the world if it's just a straight 'no' - but it would be nice to know so I'm not just banging my head against a wall :)

+9  A: 

You should be able to dump it, then reload it to a subdirectory of a new repository:

svnadmin dump http://oldrepo/ > mydump

svnadmin load --parent-dir my/new/folder http://newrepo/ < mydump

Steven Robbins
hotcopy is not a good idea if you are importing the files into an already existing repository where you want to keep the history of whatever was there before the import. "svnadmin dump/load" is the way to go.
Anders Sandvig
I've never trusted hotcopy to do anything.. I prefer the safety net of dump/load.. just giving him some options though :)
Steven Robbins
Excellent, exactly what I was looking for, thanks.
Mark B
It appears no one actually bothered to try this. You cannot do an svnadmin dump on a URL. It has to be a local repository.
Baxissimo
Well actually, I did try it - it's just that I replaced the URL's with local paths without thinking (because I was working locally on the server machine). Maybe Steve can edit his answer.
Mark B
+1  A: 

You can use tailor to import the revisions into the new repository. It checks out the code from the old repository one revision after another and commits it to the new repository.

This can also be used to convert the history of one type of version control system to another.

An tailor project file would look like this:

[DEFAULT]
root-directory = /var/tmp/tailor
verbose = true

[myproject]
source = svn:oldrepo
target = svn:newrepo
start-revision = INITIAL

[svn:oldrepo]
repository = svn://oldhost.example.com/svnroot
module = trunk
subdir = repo-in

[svn:newrepo]
repository = svn://newhost.example.com/some/path
module = trunk
subdir = repo-out

If this file is called settings.cfg, this will copy /trunk of the old repository revison by revison to the new location:

tailor --configfile=settings.cfg myproject

The target repository needs to already exist and probably should have an empty trunk subdirectory.

sth
It should in theory also be possible to use tailor to do svn to svn, but I'm having trouble getting it to work. Why would you want to do that? Because svnadmin dump will only work on local repositories. You cannot dump a repo at a URL.
Baxissimo
I added an example configuration that works for svn->svn copying. I hope you can adapt it for your case with some tweaking...
sth
+4  A: 

svnbook: Migrating Repository Data Elsewhere

Karsten