pgsql: Make install-tests target work with vpath builds

Started by Andrew Dunstanabout 6 years ago4 messagescomitters
Jump to latest
#1Andrew Dunstan
andrew@dunslane.net

Make install-tests target work with vpath builds

Also add a top-level install-tests target.

Backpatch to all live branches.

Craig Ringer, tweaked by me.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/af4ea507c3d9217579a8d75fc17f4796a9bab0bb

Modified Files
--------------
GNUmakefile.in | 1 +
src/test/regress/GNUmakefile | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)

#2Michael Paquier
michael@paquier.xyz
In reply to: Andrew Dunstan (#1)
Re: pgsql: Make install-tests target work with vpath builds

Hi Andrew,

On Sun, May 31, 2020 at 10:37:17PM +0000, Andrew Dunstan wrote:

Make install-tests target work with vpath builds

Also add a top-level install-tests target.

Backpatch to all live branches.

Craig Ringer, tweaked by me.

Please note that you have forgotten a "Discussion:" tag here.
--
Michael

#3Andrew Dunstan
andrew@dunslane.net
In reply to: Michael Paquier (#2)
Re: pgsql: Make install-tests target work with vpath builds

On 6/1/20 2:17 AM, Michael Paquier wrote:

Hi Andrew,

On Sun, May 31, 2020 at 10:37:17PM +0000, Andrew Dunstan wrote:

Make install-tests target work with vpath builds

Also add a top-level install-tests target.

Backpatch to all live branches.

Craig Ringer, tweaked by me.

Please note that you have forgotten a "Discussion:" tag here.

There wasn't really very much discussion. Do we have a policy of using
that tag for every single commit, or only when there's something of
value in the mailing list?

cheers

andrew

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Andrew Dunstan (#3)
Re: pgsql: Make install-tests target work with vpath builds

Andrew Dunstan <andrew@dunslane.net> writes:

On 6/1/20 2:17 AM, Michael Paquier wrote:

Please note that you have forgotten a "Discussion:" tag here.

There wasn't really very much discussion. Do we have a policy of using
that tag for every single commit, or only when there's something of
value in the mailing list?

There's no hard-and-fast policies about commit messages. Having said
that, I'd err on the side of linking to any related discussion, even
if there wasn't much.

regards, tom lane