Machine-specific problem with triggers in Perl

--===============1844013051==
Content-Type: multipart/alternative; 
	boundary="----=_Part_66891_11839066.1149638650328"

------=_Part_66891_11839066.1149638650328
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

   I'm having a problem with BitKeeper triggers written in Perl, and was
hoping someone on this list might have seen something similar and be able to
help.

   I'm running BitKeeper on a Windows XP / Cygwin platform, as are a number
of my coworkers.  Our repository has post-commit and post-push (I forget the
proper name of that one) triggers written in Perl.  The triggers are pretty
standard--they send a summary email to everyone in the workgroup.

   The problem is, when BitKeeper runs those triggers on my machine, it
gives the following output:

   "Bitkeeper/triggers/post-commit.mail.perl Syntax OK"

   This is exactly the same output I get if I run "perl -c" (syntax check
only) on the trigger from the root of the repository.

   If I explicitly call perl on one of the trigger files from outside of
Bitkeeper (i.e., "perl post-commit.mail.perl"), it works correctly.  It also
works if I directly call the trigger from the shell (just call "
post-commit.mail.perl").  The only time it fails is when BitKeeper tries to
run it, and then all I get is syntax checking.

   I experimented a bit and worked out the following:

1)  If I replace the trigger with a syntactically incorrect Perl script,
BitKeeper accurately reports the syntax error, supporting the conclusion
that it is somehow running Perl in syntax-checking mode.

2) If I add a shell script trigger, it runs fine, with no messages.  Just
does what it's supposed to.  The problem is specific to Perl triggers.

   c:\cygwin\bin is the first directory in my PATH environment variable, so
I know I'm getting the correct perl executable.

   Any thoughts on what might be causing this?

Thanks,
David Schwarz

------=_Part_66891_11839066.1149638650328
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br>&nbsp;&nbsp; I'm having a problem with BitKeeper triggers written in Perl, and was hoping someone on this list might have seen something similar and be able to help.<br><br>&nbsp;&nbsp; I'm running BitKeeper on a Windows XP / Cygwin platform, as are a number of my coworkers.&nbsp; Our repository has post-commit and post-push (I forget the proper name of that one) triggers written in Perl.&nbsp; The triggers are pretty standard--they send a summary email to everyone in the workgroup.
<br><br>&nbsp;&nbsp; The problem is, when BitKeeper runs those triggers on my machine, it gives the following output:<br><br>&nbsp;&nbsp; &quot;Bitkeeper/triggers/post-commit.mail.perl Syntax OK&quot;<br><br>&nbsp;&nbsp; This is exactly the same output I get if I run &quot;perl -c&quot; (syntax check only) on the trigger from the root of the repository.
<br><br>&nbsp;&nbsp; If I explicitly call perl on one of the trigger files from outside of Bitkeeper (i.e., &quot;perl post-commit.mail.perl&quot;), it works correctly.&nbsp; It also works if I directly call the trigger from the shell (just call &quot;
post-commit.mail.perl&quot;).&nbsp; The only time it fails is when BitKeeper tries to run it, and then all I get is syntax checking.<br><br>&nbsp;&nbsp; I experimented a bit and worked out the following:<br><br>1)&nbsp; If I replace the trigger with a syntactically incorrect Perl script, BitKeeper accurately reports the syntax error, supporting the conclusion that it is somehow running Perl in syntax-checking mode.
<br><br>2) If I add a shell script trigger, it runs fine, with no messages.&nbsp; Just does what it's supposed to.&nbsp; The problem is specific to Perl triggers.<br><br>&nbsp;&nbsp; c:\cygwin\bin is the first directory in my PATH environment variable, so I know I'm getting the correct perl executable.
<br><br>&nbsp;&nbsp; Any thoughts on what might be causing this?<br><br>Thanks,<br>David Schwarz<br>

------=_Part_66891_11839066.1149638650328--

--===============1844013051==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bitkeeper-users mailing list
[email protected]
http://mail.bitmover.com/mailman/listinfo/bitkeeper-users
--===============1844013051==--