Re: minimum Meson version - Mailing list pgsql-hackers

From Tom Lane
Subject Re: minimum Meson version
Date
Msg-id 1176150.1750278090@sss.pgh.pa.us
Whole thread Raw
In response to Re: minimum Meson version  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
Peter Eisentraut <peter@eisentraut.org> writes:
> On 18.06.25 19:53, Andres Freund wrote:
>> 1) We don't remove support for OS versions unless they block something

> Maybe it's worth clarifying the interpretation of this.

> For example, for the purpose of this thread, I wouldn't consider RHEL8 
> to be blocking anything at the moment.  It's technically blocking moving 
> the meson requirement past some version, but that in turn isn't really 
> blocking anything.

It's not the meson version that's the problem with RHEL8, it's the
ninja version, which is blocking our *use* of meson (and therefore
blocking removal of autoconf).

> (Also, they sometimes ship updated python or openssl versions, for 
> example, so there is also a possible difference between support in its 
> original version, support with updates, and no support at all.)

Right.  I think it's fair to say that we'll support only fully-updated
installations.

> (I initially thought that RHEL8 was a typo for RHEL7, because we still 
> support RHEL7!!  We should drop that first!)

As per Andres' proposed rule 1, we won't drop support for an old
version until it's blocking some change we want to make.  In this
context it wouldn't surprise me a bit if we end up dropping RHEL7
and RHEL8 at the same time and for the same reason (ie, lack of
new-enough meson/ninja packages).

            regards, tom lane



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: CHECKPOINT unlogged data
Next
From: Robert Treat
Date:
Subject: Re: pg_dump/pg_dumpall help synopses and terminology