From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: meson vs tarballs |
Date: | 2024-03-13 14:42:04 |
Message-ID: | 2047141.1710340924@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 13.03.24 07:42, Andrew Dunstan wrote:
>> On 2024-03-13 We 02:31, Andrew Dunstan wrote:
>>>> Alternatively, PostgreSQL can be built using Meson. This is currently
>>>> experimental and only works when building from a Git checkout (not
>>>> from a distribution tarball).
>> Ah!. Darn, I missed that. Thanks.
>> Of course, when release 17 comes out this had better not be the case,
>> since we have removed the custom Windows build system.
> Yes, this has been changed in 17.
My understanding is that pretty soon there will be no difference,
ie distribution tarballs will have the same contents as a git pull
(less the .git infrastructure). If we're planning on making that
happen for 17, perhaps we'd better get on with it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2024-03-13 15:14:50 | Re: Support a wildcard in backtrace_functions |
Previous Message | Dean Rasheed | 2024-03-13 14:32:11 | Re: MERGE ... WHEN NOT MATCHED BY SOURCE |