Geoffrey Alan Washburn wrote:
>> Well, you wanted to "encapuslate the functionality of svnadmin dump
>> and preserve hooks". A complete hot-backup, with the hooks and conf
>> files, integrated to another mirror directory seems just the thing.
>>
>> Do you want to have the svnadmin dump instead for editing reasons,
>> and a separate process for grabbing hooks and conf files?
>
> Well, I assumed that was the standard method for upgrading a
> repository from an "older" version of Subversion to a "newer" version
> of Subversion was to dump, create a new repository and then load. Does
> hotcopy do upgrades or does it just create a backup?
That question seems strange. It has to be the same version of Subversion, or
a similar one, in order to read the old repository. It then has to be a
newer version of Subversion to create it in the new format. For such a step,
I really think you need to use the "svnadmin dump" facility. Hooks and
configure scripts may not even be compatible between different versions of
subversion, although the authors have done a very good job of keeping them
consistent and flexible enough to be ported easily.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 1 23:30:18 2006