From: =?utf-8?q?C=C3=A9dric_Villemain?= <cedric@2ndquadrant.com>
Reply-To: cedric@2ndquadrant.com
Organization: 2ndQuadrant
To: pgsql-hackers@postgresql.org
Subject: Re: Bugfix and new feature for PGXS
Date: Wed, 19 Jun 2013 11:55:09 +0200
User-Agent: KMail/1.13.7 (Linux/3.8-2-amd64; KDE/4.8.4; x86_64; ; )
Cc: Peter Eisentraut <peter_e@gmx.net>,
 Craig Ringer <craig@2ndquadrant.com>
References: <201306181552.36673.cedric@2ndquadrant.com>
 <1371610091.13762.20.camel@vanquo.pezone.net>
In-Reply-To: <1371610091.13762.20.camel@vanquo.pezone.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1482403.trNayKGj9O";
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201306191155.13232.cedric@2ndquadrant.com>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

--nextPart1482403.trNayKGj9O
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Le mercredi 19 juin 2013 04:48:11, Peter Eisentraut a =C3=A9crit :
> On Tue, 2013-06-18 at 15:52 +0200, C=C3=A9dric Villemain wrote:
> > This allows for example to install hstore header and be able to
> > include them
> >=20
> > in another extension like that:
> >   # include "contrib/hstore/hstore.h"
>=20
> 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=
=20
that some header may have the same name.
If you think that it is suitable, I can do that ? (and include the clean:=20
recipe that I missed on the first shot)

Also, do we want to keep the word 'contrib' ? include/extension looks fine=
=20
too...

=2D-=20
C=C3=A9dric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - D=C3=A9veloppement, Expertise et Formation

--nextPart1482403.trNayKGj9O
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQEcBAABAgAGBQJRwYABAAoJENsgH0yzVBebYtkH/j1z5u8/I5ejezSbdNOYSFTz
ZyE2bszd3qeShWYy0v6TGsUjFmSAGpMItr6gMBOnktngDOOeG+BH6iI9lVmRD4ND
fnXHUirplX6j4NKulTI9LcGYd9d11CLtCANOpAdTbgYXjpUEmh8FeRNxMSHIUDhv
I83Xc2n6tpdQBk3O0PCrOszsF4em3wm8wrMumBHpgezaiCIVWSdER6ZacNC9yZFf
9YcN2tVkDQVLotxwRzxLy5Ox565f7UIn81CoNGYmvd6inMeV6DJe7WOEa5UZ4lkx
wuJ9atMKYVvqOK+oqwcet42Fq8pVIoNOTCyqn7/oYLex2rF84zabd/qsTwDswMo=
=kpmr
-----END PGP SIGNATURE-----

--nextPart1482403.trNayKGj9O--