On Tue, Sep 28, 2010 at 12:08 PM, Daniel Shahaf <d...@daniel.shahaf.name> wrote: > Stefan Sperling wrote on Tue, Sep 28, 2010 at 17:55:37 +0200: >> On Tue, Sep 28, 2010 at 10:08:53AM -0500, Les Mikesell wrote: >> > On 9/28/2010 9:49 AM, Stefan Sperling wrote: >> > >On Tue, Sep 28, 2010 at 04:42:50PM +0200, Daniel Shahaf wrote: >> > >>Nico Kadel-Garcia wrote on Mon, Sep 27, 2010 at 23:05:20 -0400: >> > >>>dump is very useful for using a new format, or optimizing the relevant >> > >>>database. It doesn't bring along your config tools. In fact, I'd love >> > >>>to see the "svnadmin hotcopy" factored, first to transfer the >> > >>>database, and separately to transfer configurations. >> > >> >> > >>i.e., to copy the hooks/ and conf/ directories too? Sounds like >> > >>a reasonable feature request... >> > >> >> > >>Feel free to file an issue, or send a patch, etc. >> > > >> > >Such an issue already exists: >> > >http://subversion.tigris.org/issues/show_bug.cgi?id=3299 >> > >> > It would be nice if svnsync tracked and transported them as well, >> > but kept them in a renamed location so they would not be used unless >> > you wanted to activate the copy as a replacement for the (probably >> > now defunct) original. >> >> Feel free to file an issue, or send a patch, etc. :) >> >> In any case, neither issue is trivial to solve. They need some design. > > Also: Authz. Just because I have read access to a repos, doesn't mean > I should be able to read its hooks and config. > > (particularly if that config just contains people's passwords, eg > svnserve.conf)
Especially "password" files, or user access lists. Personally, I use RCS for the config files and hook scripts inside an SVN repository. That way, an 'svnadmin hotcopy' gets those.