[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: client-side hooks

From: Miha Vitorovic <miha.vitorovic_at_gmail.com>
Date: Mon, 28 Dec 2009 12:21:34 +0100

On 12/28/2009 12:13 PM, Stefan Sperling wrote:
> On Mon, Dec 28, 2009 at 06:38:32AM +0100, Branko Čibej wrote:
>
>> Stefan Sperling wrote:
>>
>>> Client-side hooks can do very interesting things.
>>> I've seen people pick TortoiseSVN as their only client because it has this
>>> feature. Just like server-side hooks, it allows for a higher degree of
>>> automation and can reduce the error rate of the software development
>>> process if used right. It would be a useful feature for the CLI client.
>>>
>>>
>> Ah, OK, that's a different story then. Such a client-side hook API
>> should live in libsvn_client. But ... as soon as I start thinking about
>> such an API, it suddenly expands into a framework that takes over a lot
>> of stuff that we're currently doing on the client side, e.g., keyword
>> substitution and similar. Externals (shudder).
>>
>> Time to stop overengineering ...
>>
> If that happens then you're thinking too much :)
>
> You're thinking about what the hooks could be doing, but that's up
> to the user to decide, not us. We'd just need to invoke the hooks.
>
> Stefan
>
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)?
I mean, clearly a CLI svn client solution should support server (admin)
enforced client side hooks that can run on all the OSes that the CLI
client is capable of running on. And that doesn't seem like a simple
task to me.

Miha
Received on 2009-12-28 12:22:13 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.