On Sun, Feb 26, 2012 at 09:50:04PM -0500, Robert Haas wrote:
> On Sun, Feb 26, 2012 at 10:36 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> > On lör, 2012-02-25 at 14:21 +0100, Christoph Berg wrote:
> >> Well, I'm trying to invoke the extension's "make check" target at
> >> extension build time. I do have a temporary installation I own
> >> somehwere in my $HOME, but that is still trying to find extensions in
> >> /usr/share/postgresql/9.1/extension/*.control, because I am using the
> >> system's postgresql version. The build process is not running as root,
> >> so I cannot do an install of the extension to its final location.
> >> Still it would be nice to run regression tests. All that seems to be
> >> missing is the ability to put
> >>
> >> extension_control_path = /home/buildd/tmp/extension
> >>
> >> into the postgresql.conf of the temporary PG installation, or some
> >> other way like "CREATE EXTENSION foobar WITH CONTROL
> >> '/home/buildd/...'.
> >
> > Yeah, of course, the extension path is not related to the data
> > directory. So we do need some kind of path setting, just like
> > dynamic_library_path.
>
> That logic seems sound to me, so +1.
+1 here as well. I may attempt to produce a patch if this gets consensus.
--strk;
,------o-. | __/ | Delivering high quality PostGIS 2.0 ! | / 2.0 | http://strk.keybit.net -
http://vizzuality.com`-o------'