Re: Machine-specific problem with triggers in Perl
Rick Smith <[email protected]> Tue, 6 Jun 2006 17:28:43 -0700
| Newsgroups | gmane.comp.version-control.bitkeeper.user |
|---|---|
| Message-ID | <[email protected]> |
Hi, What version are you running? bk version If not bk-3.2.8, try upgrading to it. There was a problem in an old version of bk where it spawned the script with -c because the thought it was /bin/sh script. Rick On Tue, Jun 06, 2006 at 07:04:10PM -0500, David Schwarz wrote: > 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 > _______________________________________________ > Bitkeeper-users mailing list > [email protected] > http://mail.bitmover.com/mailman/listinfo/bitkeeper-users