Toby Johnson wrote:
> Max Bowsher wrote:
>
>> I am the one who first mentioned the environment variable mechanism in
>> this discussion. I agree it would be a good way to pass arbitrary
>> information to hook scripts.
>
> OK, can we concentrate on this then? I think everyone involved agrees
> that implementing a very generic mechanism to make this possible is both
> desirable and possible while not breaking older clients. If Steve/TSVN
> wants to implement some other mechanism whereby users can send client
> version or other info, that would be up to the TSVN project and the
> Subversion client wouldn't need to do anything special with particular
> variables.
Ummm, what?
Sure, I said environment variables would be a suitable way to pass
information that the server happens to have available to hook scripts.
But now you are talking about some kind of generic mechanism for marshalling
arbitrary key/value pairs from the client to the hook scripts?
I speak only for myself, not the Subversion developers in general, but my
opinion is that this is a horrible idea.
It destroys the whole principle of "Subversion clients are compatible with
Subversion servers", and makes you use a client which happens to support
whatever random things the hook scripts have been built to use.
> IMO, this would also make hook scripts much easier for Windows admins.
> Environment variables are much easier to deal with from a batch script
> than having to use either the SVN libs or svnlook to examine author,
> log, etc.
If you are finding the built in Windows scripting tools deficient (and let's
face it, they are), then both Python and Perl are well-packaged for Windows.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 11 00:37:29 2005