Peter Eisentraut <peter_e(at)gmx(dot)net> 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.  (This is pure speculation.  Personally, I certainly
> wouldn't do this, in the same way as I don't install libraries in /usr/lib
> because it makes it easier for the linker to find.)

I agree that that's the right place to put the perl & python modules
when doing a pure-default configure: it's reasonable to assume we are
installing a production system, and so we should install these modules
in the default places.  But it's a lot harder to make that argument when
doing a configure with a non-default --prefix: we may well be building a
playpen installation.  In any case there should be a way to suppress
automatic installation of these modules.

> 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, plus options on the order of
--no-install-perl (ie, build it, but don't install it).

			regards, tom lane

In response to

• Re: Build problem with CVS version at 2001-09-04 12:58:16 from Peter Eisentraut

Responses

• Re: Build problem with CVS version at 2001-09-06 15:45:25 from Peter Eisentraut

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2001-09-04 15:01:08
	Subject: Re: Table vs. row level locks confusion
Previous:	From: Doug McNaught	Date: 2001-09-04 14:46:12
	Subject: Re: Fw: Random strings

pgsql-bugs by date

Next:	From: Tom Lane	Date: 2001-09-04 14:57:16
	Subject: Re: Bug #436: backend closed the channel unexpectedly
Previous:	From: Peter Eisentraut	Date: 2001-09-04 13:06:02
	Subject: Re: Building documentation in PostgreSQL 7.2devel