I understand the concerns but I would not qualify it as "minor
developer-convenience feature".
I'm not impartial because the initial suggestion was mine, just to add
more options to be considered:
What if the generated parser/lexer be present in the tarball distributions ?
Cheers !
On 7/7/21 17:14, Tom Lane wrote:
> ilmari@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes:
>> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>>> On 04.07.21 17:58, Tom Lane wrote:
>>>> When is "some time now"?
>>> release 2.5 (2011-05-14)
>> Do we support building on RHEL6? It only ships bison 2.4, so that would
>> mean people building on that would have to install it seprately.
> A quick look through the buildfarm shows these animals that would be
> unhappy:
>
> sysname | snapshot | l gaur | 2021-07-03 22:56:25
|configure: using bison (GNU Bison) 1.875
> prairiedog | 2021-07-07 06:38:15 | configure: using bison (GNU Bison) 1.875
> locust | 2021-07-07 07:15:22 | configure: using bison (GNU Bison) 2.3
> longfin | 2021-07-07 04:39:09 | configure: using bison (GNU Bison) 2.3
> sifaka | 2021-07-07 04:33:58 | configure: using bison (GNU Bison) 2.3
> anole | 2021-07-01 15:50:38 | configure: using bison (GNU Bison) 2.4.1
> gharial | 2021-07-05 08:00:48 | configure: using bison (GNU Bison) 2.4.1
> walleye | 2021-07-07 06:55:35 | configure: using bison (GNU Bison) 2.4.2
> jacana | 2021-07-06 03:00:44 | Jul 05 23:00:49 configure: using bison (GNU Bison) 2.4.2
>
> (hmm, almost half of those are mine :-(). The main thing I take away
> from this is that Apple is still shipping 2.3, which means that requiring
> 2.5 would completely break the ability to build on macOS without using
> anything from homebrew or macports. That seems like moving the goalposts
> pretty far for a minor developer-convenience feature.
>
> regards, tom lane
