Noel Yap wrote:
>--- Karl Fogel <kfogel@newton.ch.collab.net> wrote:
>
>
>>Branko ÄŒibej <brane@xbc.nu> writes:
>>
>>
>>>Just as an example: the box I'm typing this on --
>>>
>>>
>>a laptop with WinXP --
>>
>>
>>>defines 10 different "executable" extensions. I'd
>>>
>>>
>>rather not check for
>>
>>
>>>them all.
>>>
>>>
>>How about a new APR function:
>>
>>
>
>IMHO, the "proper" way to implement such a function
>would be to look at the PATHEXT env var which, in
>itself is platform specific. I think a configuration
>file is more generic and lends itself better to
>platform independence even at the expense of a little
>added complexity.
>
That's what I thought, too. BTW, PATHEXT isn't enough -- we'd have to
check file associations, too.
>OTOH, I see little need to be able to specify more
>than one executable per hook. For example, being able
>to supply the name of one and only one pre-commit
>script should be sufficient for most (if not all)
>requirements for a pre-commit script.
>
>
I suppose that would be acceptable, yes. Then the config file would have
one section for each hook.
Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 13 01:48:50 2002