pgsql: Ah, I finally realize why Magnus wanted to add a --bindir option

Started by Nonameover 19 years ago4 messages
#1Noname
tgl@postgresql.org

Log Message:
-----------
Ah, I finally realize why Magnus wanted to add a --bindir option to
pg_regress: there's no other way to cope with testing a relocated
installation. Seems better to call it --psqldir though, since the
only thing we need to find in that case is psql. It'd be better if
we could use find_other_exec, but that's not happening unless we are
willing to install pg_regress alongside psql, which seems unlikely
to happen.

Modified Files:
--------------
pgsql/src/makefiles:
pgxs.mk (r1.8 -> r1.9)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/makefiles/pgxs.mk.diff?r1=1.8&r2=1.9)
pgsql/src/pl/plperl:
GNUmakefile (r1.27 -> r1.28)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/GNUmakefile.diff?r1=1.27&r2=1.28)
pgsql/src/pl/plpython:
Makefile (r1.25 -> r1.26)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/Makefile.diff?r1=1.25&r2=1.26)
pgsql/src/pl/tcl:
Makefile (r1.49 -> r1.50)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/tcl/Makefile.diff?r1=1.49&r2=1.50)
pgsql/src/test/regress:
GNUmakefile (r1.61 -> r1.62)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/GNUmakefile.diff?r1=1.61&r2=1.62)
pg_regress.c (r1.10 -> r1.11)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/pg_regress.c.diff?r1=1.10&r2=1.11)

#2Peter Eisentraut
peter_e@gmx.net
In reply to: Noname (#1)
Re: [COMMITTERS] pgsql: Ah, I finally realize why Magnus wanted to add a --bindir option

Tom Lane wrote:

Ah, I finally realize why Magnus wanted to add a --bindir option to
pg_regress: there's no other way to cope with testing a relocated
installation. Seems better to call it --psqldir though, since the
only thing we need to find in that case is psql.

Well, if the ecpg tests materialize, maybe not.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

#3Andrew Dunstan
andrew@dunslane.net
In reply to: Peter Eisentraut (#2)
Re: [COMMITTERS] pgsql: Ah, I finally realize why Magnus

Peter Eisentraut wrote:

Tom Lane wrote:

Ah, I finally realize why Magnus wanted to add a --bindir option to
pg_regress: there's no other way to cope with testing a relocated
installation. Seems better to call it --psqldir though, since the
only thing we need to find in that case is psql.

Well, if the ecpg tests materialize, maybe not.

Maybe installbindir or some such. As Tom has no doubt observed, this
change also manages to handle the problem we faced in running
installcheck under Msys, even when the installation is not relocated
(buildfarm does not relocate the install - it installs in the configured
path).

cheers

andrew

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Andrew Dunstan (#3)
Re: [COMMITTERS] pgsql: Ah, I finally realize why Magnus

Andrew Dunstan <andrew@dunslane.net> writes:

Peter Eisentraut wrote:

Tom Lane wrote:

Ah, I finally realize why Magnus wanted to add a --bindir option to
pg_regress: there's no other way to cope with testing a relocated
installation. Seems better to call it --psqldir though, since the
only thing we need to find in that case is psql.

Well, if the ecpg tests materialize, maybe not.

Maybe installbindir or some such.

The problem with --bindir is that it confuses the purpose with the
build/install-time bindir, which is actually nearly unrelated --- it'll
likely have a similar path tail, but path head could be completely
different. (Confusing this purpose with bindir was why I failed to grok
the point to start with.) Call it what you like so long as it ain't
bindir ...

regards, tom lane