Thanks, I'll use bat wrappers then until I can move the svn server to a real OS.
/Gunnar
Branko Čibej wrote:
> Andrew Thompson wrote:
>
>> Branko Čibej wrote:
>>
>>> Gunnar Grim wrote:
>>>
>>>> Hi,
>>>>
>>>> I'd like to write my hooks (post-commit etc) as bash scripts instead
>>>> of exe or bat files. I realize that I can make a simple wrapper bat
>>>> file for each script, that invokes bash, but I assume that I will
>>>> have slightly better performance if there was some way I could tell
>>>> subversion to skip that step and run bash directly. Anyone knows if
>>>> this is possible?
>>>
>>>
>>
>> Save your file with a recognizable extension(say .sh). Right-click it
>> and choose open with... Click the Other button, and chase down your
>> bash executable and click ok a couple of times. That should associate
>> your script with bash. Cross your fingers and commit.
>>
>> (Theory, not tested, as I haven't worked enough with svn to fiddle
>> with commit hooks.)
>
>
> Well, that theory assumes that svn uses these associations to determine
> which file is executable. It does not. Windows hooks must be .exe, .cmd
> or .bat files.
>
> (And it turns out The Book gets it wrong when it mentions .com files.)
>
> The file association thingy is an evil plot designed to compromise the
> security of your Windows box. That's why Subversion doesn't (and won't)
> use either the file assoc info or the %PATHEXT% list.
>
> -- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 9 20:41:01 2005