Re: pgxs: build infrastructure for extensions v4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgxs: build infrastructure for extensions v4
Date: 2004-08-03 23:52:49
Message-ID: 15085.1091577169@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Joe Conway <mail(at)joeconway(dot)com> writes:
> One question did arise, however. In order to use pgxs I needed to do:
> make install-all-headers
> instead of:
> make install

> I seem to recall some discussion about this, but at the time didn't
> realize the impact. IMHO pgxs support (including all needed headers)
> should be installed by default, else we won't be able to count on it
> being there when needed. Any chance we can revisit this?

AFAICS the packagers (RPM etc) will continue to think that these files
belong in a postgresql-devel RPM, and will not include them in a base
package. I'm not sure of the point of trying to force installation in
a build from source given that much of the world isn't going to be using
a source package anyway.

However, we could certainly talk about altering the default behavior
(eg, install becomes install-no-headers and install-all-headers becomes
part of the default install target).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-08-03 23:56:36 Preliminary PITR documentation available
Previous Message Joe Conway 2004-08-03 22:58:06 Re: compile warnings

Browse pgsql-patches by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-08-04 02:05:47 Re: pgxs: build infrastructure for extensions v4
Previous Message Joe Conway 2004-08-03 22:58:06 Re: compile warnings