On mar., 2010-05-25 at 19:35 -0500, Raphael Geissert wrote:
> > ./configure is a *generated* script too, if dash cannot handle it, dash
> > has to be crippled to let the other packages continue working. Unless
> > autoconf itself has already been patched to fix all of these issues when
> > regenerating ./configure from configure.ac, all this would be a waste
> > of effort anyway.
>
> It is not about whether dash can handle it or not. The bashisms don't come
> from autoconf, the come from what the author's added to configure.in{,.in}. I beg to differ, at least some of them don't come from configure.*. One example is http://people.debian.org/~geissert/source-bashisms/evolution_2.30.1.2-2.dsc where I can't really fine the >&$3 call (nor any >& for that matter) in the configure.* files. And here, just a quick test shown that: cor...@hidalgo: grep -c '>&' /usr/share/*/config.{guess,sub} /usr/share/automake-1.11/config.guess:13 /usr/share/automake-1.7/config.guess:13 /usr/share/misc/config.guess:13 /usr/share/automake-1.11/config.sub:5 /usr/share/automake-1.7/config.sub:5 /usr/share/misc/config.sub:5 cor...@hidalgo: dpkg -S /usr/share/*/config.{guess,sub} automake: /usr/share/automake-1.11/config.guess automake1.7: /usr/share/automake-1.7/config.guess autotools-dev: /usr/share/misc/config.guess automake: /usr/share/automake-1.11/config.sub automake1.7: /usr/share/automake-1.7/config.sub autotools-dev: /usr/share/misc/config.sub Interestingly, they don't seem to be caught by checkbashisms (maybe I still have a non working version?) cor...@hidalgo: checkbashisms /usr/share/*/config.{guess,sub} possible bashism in /usr/share/automake-1.11/config.guess line 95 (trap with signal numbers): trap 'exit 1' 1 2 15 possible bashism in /usr/share/automake-1.7/config.guess line 95 (trap with signal numbers): trap 'exit 1' 1 2 15 possible bashism in /usr/share/misc/config.guess line 95 (trap with signal numbers): trap 'exit 1' 1 2 15 Cheers, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
