Message-ID: <51C1BB02.8050908@gmx.net>
Date: Wed, 19 Jun 2013 10:06:58 -0400
From: Peter Eisentraut <peter_e@gmx.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: cedric@2ndquadrant.com
CC: pgsql-hackers@postgresql.org, Craig Ringer <craig@2ndquadrant.com>
Subject: Re: Bugfix and new feature for PGXS
References: <201306181552.36673.cedric@2ndquadrant.com>
 <1371610091.13762.20.camel@vanquo.pezone.net>
 <201306191155.13232.cedric@2ndquadrant.com>
In-Reply-To: <201306191155.13232.cedric@2ndquadrant.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 6/19/13 5:55 AM, Cédric Villemain wrote:
> Le mercredi 19 juin 2013 04:48:11, Peter Eisentraut a écrit :
>> On Tue, 2013-06-18 at 15:52 +0200, Cédric Villemain wrote:
>>> This allows for example to install hstore header and be able to
>>> include them
>>>
>>> in another extension like that:
>>>   # include "contrib/hstore/hstore.h"
>>
>> That's not going to work.  hstore's header file is included as #include
>> "hstore.h" (cf. hstore source code).  Having it included under different
>> paths in different contexts will be a mess.
> 
> OK.
> At the beginning I though of putting headers in include/contrib but feared 
> that some header may have the same name.
> If you think that it is suitable, I can do that ? (and include the clean: 
> recipe that I missed on the first shot)

I don't think there is any value in moving the contrib header files around.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers