Adam D. Barratt wrote:
> On Mon, 2008-03-17 at 08:26 +0000, Adam D. Barratt wrote:
>> Raphael Geissert wrote:
>> > [19:11] <Atomo64> adsb: already found the first false positives...
>> > guilty package: txt2man, guilty scripts: /usr/bin/txt2man and
>> > /usr/bin/src2man :)
>> > [20:05] <Atomo64> adsb: more: package: cvs, script: /usr/bin/rcs2log
>> > [20:06] <Atomo64> adsb: package: dirdiff script: /usr/bin/dirdiff
>> > [00:28] <Atomo64> adsb: another false positive in package: autoconf,
>> > script: ./usr/bin/autoconf
> [...]
>> > package: bastille, script: /sbin/bastille-firewall-schedule
> [...]
>> Mar 17 06:51:56 <Atomo64> adsb: ugh ugh, package: freehdl, script:
>> /usr/bin/freehdl-libtool
>> Mar 17 06:54:21 <Atomo64> adsb: heh this one is scary, package: git-gui,
>> script: /usr/bin/git-citool
>
> I believe these are all fixed in SVN, with one exception - a false
> positive function name in freehdl-libtool (and indeed ltmain.sh in
> general) due to:
>
> && $echo "X$libobj" | grep '[]~#^*{};<>?"'"'"' &()|`$[]' \
>
> Any suggestions as to how to resolve that welcome :-) The only solution
> I've come up with thus far is fudging the regex to allow &s, but I'd
> rather have the false positives than do that. :-/
Can't that be handled by the quotes-handling part of checkbashisms?
I really haven't looked at that part of the code, but my guess is that it
should be 'fairly trivial' to fix at that part rather than modifying the
check's regex.
The quotes parser should understand it as '[]~#^*{};<>?"', "'", '
&()|`$[]'
>
> Adam
>
>
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To unsubscribe, send mail to [EMAIL PROTECTED]
