Re: pgxs: build infrastructure for extensions v4 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgxs: build infrastructure for extensions v4
Date
Msg-id 15085.1091577169@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgxs: build infrastructure for extensions v4  (Joe Conway <mail@joeconway.com>)
Responses Re: pgxs: build infrastructure for extensions v4
Re: pgxs: build infrastructure for extensions v4
List pgsql-hackers
Joe Conway <mail@joeconway.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


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: compile warnings
Next
From: Tom Lane
Date:
Subject: Preliminary PITR documentation available