pgsql: Use += not = to set makefile variables after including base make

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use += not = to set makefile variables after including base make
Date: 2015-05-18 00:04:48
Message-ID: E1Yu8Y4-00016d-MA@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use += not = to set makefile variables after including base makefiles.

The previous coding in hstore_plpython and ltree_plpython wiped out any
values set by the base makefiles. This at least had the effect of running
the tests in "regression" not "contrib_regression" as expected. These
being pretty new modules, there might be other bad effects we'd not
noticed yet.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/b14cf229f4bd7238be2e31d873dc5dd241d3871e

Modified Files
--------------
contrib/hstore_plpython/Makefile | 4 ++--
contrib/ltree_plpython/Makefile | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2015-05-18 01:22:18 pgsql: Fix failure to copy IndexScan.indexorderbyops in copyfuncs.c.
Previous Message Tom Lane 2015-05-17 19:55:10 pgsql: Release notes for 9.4.2, 9.3.7, 9.2.11, 9.1.16, 9.0.20.