This was discussed on the dev@ list long ago, and we decided not to do
it for many reasons (imho, good reasons). I don't have the archive
links, unfortunately, sorry not to be able to give you a convenient
pointer...
-Karl
"Walter Nicholls" <walter.nicholls@cornerstone.co.nz> writes:
> It occurs to me that this (client-side hooks) would actually be really
> useful. A wrapper for svn(.exe) would work as long as the command-line
> clients is used for everything. A hook system could also be used by the
> GUIs such as Rapidsvn/Eclipse/Tortoise etc.
>
> I know, I know, the post-1.0 bucket. I suspect implementing this would
> not be easily. Finding the place to put the hooks wouldn't be too hard,
> but making it reliable and working well (including having hooks modify
> the Subversion client behaviour - eg prevent a commit if certain
> conditions are or aren't met) would be a headache.
>
> I can't off the top of my head think of anything which a wrapper
> couldn't do - however it might be as hard or harder than writing a whole
> new client (eg you might need to determine which files are being
> committed, parse the text output of svn up or svn status). Might it not
> be easier to hack the source for the svn client program? <g>
> - Walter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 8 22:44:32 2004