On Nov 14, 2007 1:12 PM, Brad Stiles <bradstiles@bellsouth.net> wrote:
> > > Setting up svnserve.exe as a service is a breeze (takes about 15 minutes, 12
> > > of them figuring out the steps). Scripting can be in any language that runs on
> > > Windows.
> >
> > Unfortunately, this is one of the hoops that Windows folks have to
> > jump through. SVN on Windows only recognizes .exe, .bat and .cmd as
> > executable file types.
>
> So, even if I have a file extension associated with an EXE, such as .pl with 'Perl.exe', it won't run unless I explicitly specify 'perl.exe'?
Correct. 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.
Remember that hooks run with an empty environment, so the path to your
Perl (or Python, or Ruby, or Windows Script Host) interpreter isn't
readily known and nor would the paths to any dependent libraries.
I spoke (emailed) with a couple of the SVN devs about adding .WSF
support while back and we ultimately decided it wasn't practical or
possible to implement in a way that would work well for everyone -
same obstacles with Perl, et al. I wonder if PowerShell might be
possible though.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 14 19:22:49 2007