mark benedetto king <bking@answerfriend.com> writes:
> On Sun, Dec 15, 2002 at 04:52:23PM +0000, Philip Martin wrote:
> > How is this going to work when a repository is dumped/loaded? Should
> > a dump/load change the UUID? Should the UUID be dumped? There would
> > appear to be cases where we want the loaded repository to have the
> > same UUID as the dumped repository, and other cases where they should
> > be distinct.
> >
>
> Sounds like we need one or more of the following:
>
> 1.) boolean option to dump for whether to include the UUID
> 2.) boolean option to load for whether to use the UUID
> 3.) "svnadmin reposid"
>
> (1) and/or (2) should be enough, but I have a feeling at least one user
> will accidentally overwrite their repository's UUID, thus invalidating
> all WCs. It might be nice to give them (3) to fix that sort of problem.
>
> What would you suggest?
I'd suggest that 'svnadmin dump' and 'svnadmin load' do nothing with
UUIDs, but admit to not having invested much thought into the matter.
The following is just my immediate reaction.
I'd like 'svnadmin create' to make a repository layout that generates
the UUID in a text file in the top directory (sibling of 'README' and
'format'). And if people want to dump and load a repository, they
should remember to copy over the UUID file when they also copy over
such things as the hook scripts.
Another similar suggestion would be to get our repository config-file
in place, which the UUID as one of the "[general]" options present in
that human-hackable text file.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 16 04:49:23 2002