| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Installation of regress.so? |
| Date: | 2021-05-21 12:38:50 |
| Message-ID: | 08dcdacc-38c7-cb40-4627-37880b850ae7@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/20/21 7:58 PM, Michael Paquier wrote:
> On Thu, May 20, 2021 at 09:30:37AM -0400, Tom Lane wrote:
>> I'd be okay with it being some sort of non-default option.
> Okay. It would be possible to control that with an environment
> variable. However I am wondering if it would not be more user-friendly
> for automated environments if we had a configure switch to control
> when things related to the tests are installed or not. Say a
> --with-test-install?
That seems a bit tortured. Why should you have to make the decision at
configure time? ISTM all you need is an extra make target that will
install it for you, or a make variable that controls it in the existing
install target.
e.g. make INSTALL_REGRESS_LIB=1 install
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | osumi.takamichi@fujitsu.com | 2021-05-21 12:44:31 | RE: Forget close an open relation in ReorderBufferProcessTXN() |
| Previous Message | Andrew Dunstan | 2021-05-21 12:29:14 | Re: multi-install PostgresNode fails with older postgres versions |