> Tom Lane writes:
>
> > > What we probably want is some configure switch that switches between the
> > > current behaviour and the behaviour you want.
> >
> > I'd suggest --prefix-like options to determine installation locations
> > for the perl and python modules,
>
> Basically, I was envision
Tom Lane writes:
> > What we probably want is some configure switch that switches between the
> > current behaviour and the behaviour you want.
>
> I'd suggest --prefix-like options to determine installation locations
> for the perl and python modules,
Basically, I was envisioning some option li
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> This is a very valid concern, and it's been bugging us, too. The problem
> is that by default, the majority of users would probably want the Perl and
> Python modules to be put in the default place where they're easy to find
> for the interpreter. (
John Summerfield writes:
> To my dismay some components don't honour the "--prefix=/tmp/postgresql"
> specification and try to install in some other location.
>
> I'd much prefer for the perl and python components to install into the
> location I specified, and to leave me to discuss with Perl a
