Best approach to break up a repository

Hi,

   For some time now we've been lumping projects together in the same
repository and serving them up using apache. So our repository at
/svn_data/data will look like this

  /
    /project_A
      /trunk
      /branches
      /tags
    /project_B
      /trunk
      /branches
      /tags
     ...

   And apache will serve that up with a directive like 'SVNPath
/svn_data/repo/data'

   However, this is becoming a bit of a pain to work with for various
reasons (e.g., replicating project_B, moving projects between sites) and
I'd like to break each of those projects into separate repositories.
Given the number of designers we have, it's a bit unreasonable to expect
everyone to recreate every workspace so I'd like to keep all URLs the same.

   So I'd like to have repositories at /svn_data/repo/project_A,
/svn_data/repo/project_B, /svn_data/repo/project_C, etc. I've written
something that can dump/load each one of the projects above and add
empty revisions to keep the revisions the same, so I end up with
repositories like

/svn_data/repo/project_A:

  /
    /project_A
      /trunk
      /branches
      /tags

/svn_data/repo/project_B:

  /
    /project_B
      /trunk
      /branches
      /tags

   If I add something to my apache conf like 'SVNParentPath
/svn_data/repo', but this leads to URLs that end with
'project_A/project_A' (since 'project_A' is the root directory of the
repository). If I try to modify my dump/load script to modify the path
to drop 'project_A' then that breaks everyone's workspace.

   Is there any approach I can take to break up repositories and keep
workspaces intact? Does anyone have experience with breaking up a
repository like this?

--Mattius McLaughlin
Received on 2012-03-01 22:47:18 CET