Duncan Booth wrote:
> Anyway, my point is that if Subversion followed the same rules as the rest
> of windows it would be much easier to write hook scripts in the scripting
> language of your choice. Administrators of Windows-based repositories could
> do what they'd expect to work and have it work: e.g. add .PY to pathext and
> then just write the scripts in Python.
If I could quote Andy from an earlier message:
> The source for the hook-handling code in Subversion only
> looks for .exe, .cmd and .bat. Windows is able to execute these
> directly, without an add-on interpreter, so it can call them directly.
> Windows doesn't have an execute bit on file permissions like *NIX
> does.
To elaborate on what he was saying:
the Subversion server is not a console application and Windows only
supports *directly* executing those file types he listed. What you are
talking about (PATHEXT) is strictly the *console* support and is outside
of what Subversion currently is capable of doing. It has nothing to do
with "follow[ing] the same rules as the rest of [W]indows" and
everything to do with the way M$oft chose to partition certain features
to the shell/console layer.
Besides, it is trivial to create a .cmd file in Perl (for example) that
is both the Windows .cmd file and the Perl script. I'm sure it is
possible to do the same thing with other interpreted languages.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 15 15:50:56 2007