Re: monad hook scripts

> I would prefer to actually wait until it's released

Fair enough.

> this would require SVN to deduce the path to powershell.exe
> in order to execute .ps1 files as hook scripts.

Or require the user to map .ps1 files to powershell.exe for this
feature to work.

> set PSEXE = "C:\Program Files\Windows Powershell\1.0\powershell.exe"
> %PSEXE% %1 %2

Probably not optimal, since that batch script always exits with code 0
regardless of what the ps1 script returns.

> Also, may I interest you in my Powershell tab completion for svn.exe?

Neat! :-)

> is there an interest in adding an option to the repository
> config file of what kind of hook-scripts one would want to
> run on Windows?

I think that arbitrary hook script file extension support on Windows
would be neat. :-)

> It feels that if it is configurable on each repos, there
> wouldn't be much of a security risk. Or would it?

With sane defaults, I can't see any.

> If there is interest, I feel I'm up for the task of
> presenting a proposed design, and following implementation.

Writing a 5-line .bat per hook script won't kill anyone.

OTOH, if you're looking for a bite-size task to contribute to the
Subversion project, this would be an easy way to add another bullet to
the "new features in 1.4.1" list. The bullet could even briskly
mention support for Monad (and Python) scripts as an example, just to
show the world that the Subversion project is one step ahead of
everyone else ;-).

(I'm not a svn dev, so I cannot endorse nor bless the project in any way.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 21 08:01:36 2006