| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: List TAP test files in makefiles |
| Date: | 2025-08-23 15:23:21 |
| Message-ID: | 2749f1e0-f745-465e-bbe3-bc55f9e76140@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-08-23 Sa 10:38 AM, Andres Freund wrote:
> Hi,
>
> On 2025-08-23 10:17:59 -0400, Tom Lane wrote:
>
>> We should be striving to make the meson system as easy to use as
>> autoconf/make, not trying to attain parity by making the latter experience
>> worse.
> FWIW, I find the autoconf/make test run experience completely unusable. It
> literally is made me embark on getting away from it. I don't understand how
> people stand it.
>
Honestly, they both have annoyances and points where it's easy to get
into the weeds. There are definitely cases where meson has left me
scratching my head.
But I think this is really analogous to adding a new object file. That
needs to be added to the Makefile as well as the meson.build file, and I
don't see why tests shouldn't work the same. That might be slightly
annoying, but it would be way down on my list.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-08-23 16:11:51 | Re: List TAP test files in makefiles |
| Previous Message | jian he | 2025-08-23 15:04:42 | Re: PoC: pg_dump --filter-data <file> (like Oracle Where Clause on RMAN for specific tables) |