Re: PG_TEST_EXTRA and meson
От | Tom Lane |
---|---|
Тема | Re: PG_TEST_EXTRA and meson |
Дата | |
Msg-id | 3573037.1721239891@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: PG_TEST_EXTRA and meson (Jacob Champion <jacob.champion@enterprisedb.com>) |
Ответы |
Re: PG_TEST_EXTRA and meson
|
Список | pgsql-hackers |
Jacob Champion <jacob.champion@enterprisedb.com> writes: > On Wed, Jul 17, 2024 at 8:01 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> The existing and documented expectation is that PG_TEST_EXTRA is an >> environment variable, ie it's a runtime option not a configure option. >> Making it be the latter seems like a significant loss of flexibility >> to me. > I think/hope we're saying the same thing -- developers should not be > forced to lock PG_TEST_EXTRA into their configurations; that's > inflexible and unhelpful. Indeed. > What I'm saying in addition to that is, I really like that I can > currently put a default PG_TEST_EXTRA into my meson config so that I > don't have to keep track of it, and I do that all the time. So I'm in > favor of the "option 3" approach. Ah. I have no particular objection to that, but I wonder whether we should make the autoconf/makefile infrastructure do it too. regards, tom lane
В списке pgsql-hackers по дате отправления: