| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [RFC] building postgres with meson -v8 |
| Date: | 2022-03-28 23:11:40 |
| Message-ID: | 20220328231140.7ylalxc76zli6p46@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-03-28 18:58:19 -0400, Tom Lane wrote:
> If we can commit meson build infrastructure without removing the
> existing infrastructure, then the buildfarm can continue to work,
> and we can roll out support for the new way slowly.
I think it's not a huge issue to have both for a while. Of course it's
annoying to have to update two files when adding a source file, but it's not
the end of the world for a limited time. IMO.
> It'd be fairly impractical to expect all buildfarm animals to update
> instantly anyhow.
And development workflows. I expect some unforseen breakages somewhere, given
the variety of systems out there.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-03-28 23:25:51 | Re: SQL/JSON: functions |
| Previous Message | Tom Lane | 2022-03-28 22:58:19 | Re: [RFC] building postgres with meson -v8 |