[Pgpool-hackers] hardcoded values in configure script

[Yoshiyuki Asaba]

Hi,

From: David Fetter <david at fetter.org>
Subject: Re: [Pgpool-hackers] hardcoded values in configure script
Date: Thu, 5 Oct 2006 19:36:45 -0700

> On Fri, Oct 06, 2006 at 11:05:16AM +0900, Yoshiyuki Asaba wrote:
> > Hi,
> > 
> > From: Devrim GUNDUZ <devrim at commandprompt.com>
> > Subject: Re: [Pgpool-hackers] hardcoded values in configure script
> > Date: Thu, 05 Oct 2006 15:17:01 +0300
> > 
> > > On Thu, 2006-10-05 at 17:07 +0900, Yoshiyuki Asaba wrote:
> > > > OK. If pg_config exists, default values are determined by
> > > > pg_config. If not, these are fixed path. Does anyone have any
> > > > comment to the attached patch? 
> > > 
> > > I'm against this. If pg_config does not exist in $PATH, then
> > > configure should stop and ask for a valid path for pg_config. I
> > > think this will be better.
> > 
> > Do you think a situation that libpq is installed only?
> > 
> >   % cd postgresql-x.x.x/
> >   % ./configure
> >   % cd src/interfaces/libpq
> >   % make install
> > 
> > So I think I need "--with-pgsql" option if pg_config does not
> > installed.
> 
> I think we should require pg_config to be installed and in $PATH, and
> should stop if either of those things do not hold.
> 
> > Then configure checks libpq. If it does not exist, configure stops.
> 
> Anything not using pg_config has too many moving parts, and will be
> fragile.

Sorry for the delay.

We will release pgpool-II 1.0.2. The default values are determined by
pg_config in pgpool-II 1.0.2.

Next, with-pgsql option will be removed from configure script in
pgpool-II 1.1. Or with-pgconfig option will be added.
--
Yoshiyuki Asaba
y-asaba at sraoss.co.jp