[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best approach to break up a repository

From: Ryan Schmidt <subversion-2012a_at_ryandesign.com>
Date: Fri, 2 Mar 2012 15:23:48 -0600

On Mar 2, 2012, at 12:54, Mattius McLaughlin wrote:

>
>
> On 03/01/12 19:40, Ryan Schmidt wrote:
>> 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.
>>
>>
> I know it's not necessarily best practice, but one could get around this with a svnadmin setuuid $old-uuid, no?

Unless the new repository's history is identical to the old repository, it must not have the same UUID; doing so would confuse clients and existing working copies.
Received on 2012-03-02 22:24:29 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.