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

Re: Using VBScript for hooks? pre-revprop-change.vbs?

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-08-15 18:55:44 CEST

On 8/15/07, Tom Malia <tommalia@ttdsinc.com> wrote:
> Thanks for the response. So this sounds like a real headache. I suppose I
> could install Perl on the machine and use Perl scripts but I hate having to
> juggle a dozen different languages if I don't have to.
>
> Do you happen to know if you can write VB6 EXE's that will work as command
> hook programs? I know that VB6 has the same problem when it comes to the
> fact that it's actually running inside it's own virtual machine so I'm not
> sure if it can properly take command line arguments and return the correct
> exit codes... but if it could that would be a lot easier for me.

VB6 EXEs are real EXEs as far as the shell, etc. are concerned so you
should be fine doing that as long as you can parse the arguments
(which is very doable, I think I did it once a long time ago). The
exit codes shouldn't be a problem either - only issue you might have
is tapping into stderr instead of stdout.

> What about "Bash" on windows? What would I need to do to be able to run the
> Bash files as they are in windows? I assume something can be installed to
> allow this?

I think you'd have to run your server in a cygwin environment which
understands that those scripts are executables. On Windows, bash
scripts require an interpreter just like WSH scripts - plus, from what
I recall reading the source, the libraries don't look for the .sh
extension on Windows.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 15 18:53:45 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.