Re: dash and hidden bashisms in configure scripts

2021-11-16 Thread Zack Weinberg
Speaking as the /de facto/ upstream maintainer of autoconf, is there anything we could do from our end to make it easier for dash to turn $LINENO back on? I don't have a lot of time to work on autoconf at the moment, but this particular issue is important to me. I'd like to see all the configu

Re: dash and hidden bashisms in configure scripts

2021-11-10 Thread Johannes Schauer Marin Rodrigues
Quoting Richard Laager (2021-11-10 20:16:31) > Can we just enable LINENO in dash then, let the other packages FTBFS, and > people who care about the packages that FTBFS can either: in the best case, a package will FTBFS but it can also happen that the configure script will just do something differ

Re: dash and hidden bashisms in configure scripts

2021-11-10 Thread Dagfinn Ilmari Mannsåker
"Andrej Shadura" writes: > Well, we might make bash non-essential at one point. OTOH development > systems are likely to have it anyway. A compromise could be to make it build-essential instead. - ilmari

Re: dash and hidden bashisms in configure scripts

2021-11-10 Thread Richard Laager
On 11/10/21 12:50 PM, Andrej Shadura wrote: On Wed, 10 Nov 2021, at 19:18, Sam Hartman wrote: I understand that it's generally better to fix bashisms in configure scripts. Is it possible to force autoconf to prefer bash for a given configure script if it's difficult or undesirable to fix bashism

Re: dash and hidden bashisms in configure scripts

2021-11-10 Thread Sam Hartman
> "Andrej" == Andrej Shadura writes: Andrej> Hi all, Yesterday I uploaded dash with LINENO feature Andrej> switched on again, which has the side effect of exposing Andrej> bashisms in configure scripts. Previously, they were Andrej> obscured by the fact that autoconf requires