On Mon, Dec 28, 2009 at 01:10:29PM +0100, Miha Vitorovic wrote:
> On 12/28/2009 01:03 PM, Stefan Sperling wrote:
> >On Mon, Dec 28, 2009 at 12:21:34PM +0100, Miha Vitorovic wrote:
> >>I'm just a lurker, so my apologies if I'm missing something obvious,
> >>but isn't it much simpler to support client side hooks on a Windows
> >>only client (like Tortoise clearly is)?
> >It's up to the authors of hook scripts to make sure they run on the
> >machines they need to run on.
>
> True, but to make it useful from admin point of view (at least if
> I'm the admin), is to have hooks on the server, so that each client
> connecting to the repository gets them.
Why is that needed to make it generally useful?
You need to install svn before running svn. You can install the hooks
on your users' machines while installing svn. So you can use this
feature even if the Subversion server itself does not function as
a central distribution point for these scripts.
svn can also run external diff/merge tools, which need to exist on the
client machine. Same problem. Yet I haven't heard anyone complain
that these tools cannot be controlled from the server's end.
> Otherwise, what is the point
> of hooks if it is up to the user to install them, if they want to?
> Such hooks would be no different from wrapper scripts.
You can think of those hooks like wrapper scripts if you want.
But called at defined points in svn's execution, with a known
set of arguments, and the ability to abort svn's execution.
Stefan
Received on 2009-12-28 13:35:30 CET