On 06.08.2010 16:30, Hyrum K. Wright wrote: > On Fri, Aug 6, 2010 at 9:24 AM, Greg Stein <gst...@gmail.com> wrote: > >> On Fri, Aug 6, 2010 at 10:15, Ramkumar Ramachandra <artag...@gmail.com> >> wrote: >> >>> Hi Greg, >>> >>> Greg Stein writes: >>> >>>> Why would an admin install a hook to allow changing a UUID? Why would >>>> a UUID be allowed to change over time? If a UUID is supposed to be >>>> changed, then why wouldn't that admin just do it himself? Why does >>>> this have to be allowed remotely? >>>> >>> Agreed- this feature has a very narrow usecase. Anyway, since I >>> started the thread, let me explain the motivation for this feature. It >>> derives from `svnrdump` -- Anybody without administrative priviliges >>> can actually mirror a complete Subversion repository using `svnrdump >>> dump | svnrdump load` quite efficiently. Let's say some sponsor wants >>> to provide a mirroring service- with the proposed feature the person >>> will simply have to create a blank repository and enable >>> pre-revprop-change/ pre-uuid-change on and wait for someone to load >>> the content into that repository. After the intial mirroring is done, >>> he can always turn off the pre-uuid-change. It's probably a >>> "dangerous" feature, and I don't know if it's worth the trouble. >>> >> I disagree that the UUID should be mirrored. You're loading a *NEW* >> repository. Thus, it should not have the same UUID as the original. >> The original continues to exist. Having two repositories with the same >> UUID is just wrong. That is contrary to the entire design principle.. >> > Agreed. *Universally Unique* Identifier. >
Ahem. You guys have forgotten about Justin's RW-master/RO-slave replication hack, which *requires* the slave repositories to have the same UUID as the master. And that 'svnadmin load' has both --ignore-uuid and --force-uuid. -- Brane
