Hi, On 2025-08-23 10:17:59 -0400, Tom Lane wrote: > Andres Freund <and...@anarazel.de> writes: > > On 2025-08-23 11:57:37 +0500, Andrey Borodin wrote: > >> What is the downside of the approach where meson uses t/*.pl wildcard? > > > In meson you can't do wildcards at "configure" time, since wildcards do not > > allow reliable detection of when re-configure is needed. > > But ... what "re-configuration" is needed when adding a new test file?
In meson, not autoconf/make. The test runner doesn't parse the meson.build files, that's done once when running configure. After that there's a table of tests that need to be run that gets used when you type ninja/meson test. > 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. Greetings, Andres Freund
