[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: monad hook scripts

From: Andreas Magnusson <andreas.ch.magnusson_at_home.se>
Date: 2006-06-16 18:55:37 CEST

Arild Fines wrote:
> Given that the Powershell installer does not associate .ps1 with
> powershell.exe by default (for security reasons), it seems to me that this
> would require SVN to deduce the path to powershell.exe in order to execute
> ..ps1 files as hook scripts. I have a feeling such a change would be
> considered too windows-specific.
> You can of course run Powershell scripts as hook scripts today the same way
> you would run any other unsupported script type, by creating a batch file
> that invokes Powershell with the correct parameters:
> [[
> set PSEXE = "C:\Program Files\Windows Powershell\1.0\powershell.exe"
> %PSEXE% %1 %2
> ]]
> Also, may I interest you in my Powershell tab completion for svn.exe?
> http://arildf.spaces.msn.com/blog/cns!E99F8B43533149B0!109.entry?_c11_blogpa
> rt_blogpart=blogview&_c=blogpart#permalink
> --
> Arild

Or perhaps even better, 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? Some people have Perl or Python installed already (or
... insert favorite script language), and it just feels so "dirty" to
create a .cmd file that only does what Subversion /could/ do already (if
there was an interest in it).
It feels that if it is configurable on each repos, there wouldn't be
much of a security risk. Or would it?
If there is interest, I feel I'm up for the task of presenting a
proposed design, and following implementation.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 16 18:56:24 2006

This is an archived mail posted to the Subversion Dev mailing list.