On Mar 1, 2012, at 15:46, Mattius McLaughlin wrote: > 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.
There's no choice; when you split the big repository into smaller repositories, each repository must be given its own UUID (Universally Unique IDentifier), different from the big repository's UUID. A working copy is matched to a particular repository by UUID. Once you have new repositories, you must check out new working copies. No exceptions. > 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. Everyone's working copy is already broken by splitting the repository, so you may as well rearrange. svndumptool can help, or you can simply "svn mv" things into place.