On Mon, Dec 10, 2012 at 3:53 PM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Mon, Dec 10, 2012 at 12:47 PM, Daniel Shahaf <d...@daniel.shahaf.name> > wrote: [...]
>> The argument is that a Subversion server should be enforcing >> Subversion's invariants. >> >> That said, I'm not opposed to doing it via standard hooks. It's a good >> way to introduce the feature in a way that allows more easily changing >> it before it hits the APIs and their strict compatibility rules. > > Yes, that would be fine I think. I like Ivan's suggestion of creating > a new standard 'svnhooks' program or something like that, which can > then be part of standard distributions. > I'd like to share my thoughts about 'svnhooks' if someone is going to implement it. Introduce svnhooks program with the separate subcommand for each hook kind: 'pre-commit', 'post-comit', 'pre-lock', 'pre-unlock" and etc. The polices for svnhooks program defined in conf\svnhooks.conf file. This makes very easy for user to use svnhooks: just add line 'svnhooks HOOK-TYPE $*' in each hook and tweak svnhooks.conf configuration file. svnhooks configuration file has separate section for each policy. For example: [[[ [check-eol-normalization] enable = yes [rev-propchange] enable = yes users = svnsync [edit-log-message] enable = yes users = admin, @author ]]] -- Ivan Zhakov