| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow controlling location of tmp_install |
| Date: | 2017-01-09 19:13:02 |
| Message-ID: | afa13696-514b-30d5-009d-e9d4041b8e6c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/7/17 8:52 PM, Jim Nasby wrote:
> I've now moved my normal install locations to somewhere I can exclude
> from mds and what-not, but I don't see any way to do that with
> tmp_install. Is there a trick here I'm missing, or should I change
> Makefile.global.in to check for an environment variable?
tmp_install is hardcoded in a handful of places, but it might be
reasonable to refactor that.
Then again, couldn't you just exclude the top-level directory of the
source checkout from Spotlight?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-01-09 19:22:14 | Re: Increase pltcl test coverage |
| Previous Message | Tom Lane | 2017-01-09 19:10:25 | Re: ALTER TABLE .. ALTER COLUMN .. ERROR: attribute .. has wrong type |