Bug#463193: checkbashisms: script $filename does not appear to be a /bin/sh script on csh scripts and others

2008-02-01 Thread Raphael Geissert
On 30/01/2008, Adam D. Barratt [EMAIL PROTECTED] wrote: Hi, Raphael Geissert wrote, Wednesday, January 30, 2008 3:07 AM On scripts with a /bin/csh shebang and other scripts with a non /bin/{sh,ash,dash} shebang checkscripts quits without processing them. The portion of code is: elsif

Bug#463193: checkbashisms: script $filename does not appear to be a /bin/sh script on csh scripts and others

2008-01-30 Thread Adam D. Barratt
Hi, Raphael Geissert wrote, Wednesday, January 30, 2008 3:07 AM On scripts with a /bin/csh shebang and other scripts with a non /bin/{sh,ash,dash} shebang checkscripts quits without processing them. The portion of code is: elsif ($interpreter !~ m,/(sh|ash|dash)$,) { It should instead use

Bug#463193: checkbashisms: script $filename does not appear to be a /bin/sh script on csh scripts and others

2008-01-29 Thread Raphael Geissert
Package: devscripts Version: 2.10.13 User: [EMAIL PROTECTED] Usertags: checkbashisms On scripts with a /bin/csh shebang and other scripts with a non /bin/{sh,ash,dash} shebang checkscripts quits without processing them. The portion of code is: elsif ($interpreter !~ m,/(sh|ash|dash)$,) { It

Bug#463193: checkbashisms: script $filename does not appear to be a /bin/sh script on csh scripts and others

2008-01-29 Thread Peter Samuelson
[Raphael Geissert] On scripts with a /bin/csh shebang and other scripts with a non /bin/{sh,ash,dash} shebang checkscripts quits without processing them. Errr ... what? Checking a csh script for bashisms is like checking a Python program for bashisms. The syntax just isn't similar enough