Re: List TAP test files in makefiles

On 2025-Oct-28, Michael Paquier wrote:

> IMO, we should tackle this problem the other way around: what would it
> take to have meson build a list of the TAP files in t/ based on an
> automated rule when tests.tap is defined?

Maybe what we need is a single source of truth that is used both by
Makefiles and meson: say, a file named "testlist" which contains lines
like

regress = foo bar baz
tap = t/001_foo.pl t/002_bar.pl

(possibly with backslash-escaped newlines) and so on, which is processed
by each build system in the way that it needs.  This way, whichever
system is used by a developer, either the test will run because they
changed this one file, or it won't.

I don't know how much scaffolding is needed to make this work, but I
don't think it would be too bad.

IIRC Andres has complained about the Makefiles using t/*.pl to determine
the tests to run.  This would also solve that problem.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"I suspect most samba developers are already technically insane...
Of course, since many of them are Australians, you can't tell." (L. Torvalds)