On Tue, Feb 21, 2012 at 10:34:42PM +0100, Dimitri Fontaine wrote: > Sandro Santilli <s...@keybit.net> writes: > > On Tue, Feb 21, 2012 at 10:21:17AM -0500, Tom Lane wrote: > >> Sandro Santilli <s...@keybit.net> writes: > >> > I'm trying to understand what options I have to test "CREATE EXTENSION" > >> > w/out installing the extension files in their final destination. > >> > >> There aren't any. Generally speaking, if you want to be testing an > >> extension, you should be doing it in a test installation anyway; > >> so I don't see what's the objection to sticking the files into the > >> installation's real SHAREDIR. > > > > We do a staged installation of the extension library and scripts > > in an ad-hoc dir which does not match the built-in SHAREDIR of PostgreSQL. > > > > It works fine for testing the extension directly sourcing the scripts. > > It's only "CREATE EXTENSION" that doesn't play nicely with that setup. > > Please see the "inline extension" thread where answers to your problem > have been discussed. > > https://commitfest.postgresql.org/action/patch_view?id=746
I'm not really looking for "inline extensions". I do want to install the extension objects somewhere, just NOT in the PostgreSQL builtin SHAREDIR but in an arbitrary staging directory to use for QA the extension before distribution. --strk; ,------o-. | __/ | Delivering high quality PostGIS 2.0 ! | / 2.0 | http://strk.keybit.net `-o------' -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
