Pre/Post Checkout/Update hooks...

I guess I should have really sent this to dev mailing list,
as it's more a question of why than of how.

I had posted a question on the users mailing list wondering
if there were any plans to create pre/post checkout/update
scripts to be a part of the subversion hooks library of
calls.

This would allow for a finer level of control when it comes
to logging and controlling access to code that the apache
logs and AuthzSVNAccessFile directive really don't provide.
(ie.. who gets access to what and when).

The reply to the user post I made had the suggestion of
using the custom logging features that will be comming
out soon, but this really isn't a hook that could stop an
action if it's undesireable.

http://svn.haxx.se/users/archive-2005-10/0099.shtml

I guess my question is... what's the impetus for not
providing those 'read' hooks? It seems that people in
the past have asked for these hooks, but not so clean work-
arounds were suggested. Is there a philisophical reason for
not providing them, or an implementation reason?

filipe

ps: Please don't take the above a critisism; if anything
a 'feature request'. Subversion is a great resource and I
look forward to future releases.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 5 14:18:15 2005