Hi,
On Sun, 2008-02-10 at 01:45 -0600, Raphael Geissert wrote:
> While checking the results of my last archive wide checkbashisms check I've
> noticed some strange results such as:
These are all being flagged by a test intended to catch arguments being
passed to "sourced" scripts - e.g. ". foo bar". I've modified the check
to provide a more useful explanation.
> > possible bashism in ./usr/bin/bsetbg line 365 ():
> > . $HOME/.bsetbgrc 2>/dev/null
This was due to an oversight when resyncing with lintian recently, which
I've fixed.
> > possible bashism in ./etc/init.d/courier-pop line 58 ():
> > . ${sysconfdir}/pop3d; \
>
> > possible bashism in ./etc/init.d/courier-pop-ssl line 68 ():
> > . ${sysconfdir}/pop3d-ssl ; \
>
> > possible bashism in ./usr/bin/guilt-prev line 7 ():
> > . `dirname $0`/guilt
> > possible bashism in ./usr/bin/guilt-pop line 7 ():
> > . `dirname $0`/guilt
> > possible bashism in ./usr/bin/guilt-init line 9 ():
> > . `dirname $0`/guilt
> > possible bashism in ./usr/bin/guilt-add line 7 ():
> > . `dirname $0`/guilt
> > possible bashism in ./usr/bin/guilt-import line 7 ():
> > . `dirname $0`/guilt
>
> All of the above are fine but by some reason are being reported as bashisms.
Fixed. They'll also all be reported by lintian, so I'll make the
maintainers aware.
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
