Skip site navigation (1) Skip section navigation (2)

Re: A simpler way to configure the source code?

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Christopher Kings-Lynne'" <chriskl(at)familyhealth(dot)com(dot)au>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>
Cc: "'PostgreSQL Development'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A simpler way to configure the source code?
Date: 2002-01-31 08:35:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

> -----Original Message-----
> From: Christopher Kings-Lynne [mailto:chriskl(at)familyhealth(dot)com(dot)au] 
> Sent: 31 January 2002 01:34
> To: Dave Page; 'Peter Eisentraut'
> Cc: 'PostgreSQL Development'
> Subject: Re: [HACKERS] A simpler way to configure the source code?
> > > I feel having the "fringe features" more tested is a 
> great idea, and 
> > > will lead to a better PostgreSQL, and therefore happier 
> users.  :)  
> > > A friendly, and decently-easy-to-user interactive setup (Linux 
> > > "menuconfig" kernel style?) would be beneficial.
> > >
> > > If it doesn't add signifcant overhead to maintenance, and is very 
> > > portable, it sounds to me like a good idea.
> > >
> >
> > +1 (not that this is a vote :-) )
> Hmmm...yuck.  I think a --with-everything is a good idea, but 
> surely all that needs be done is make the regression test 
> test everything?  It's annoying little setup scripts that 
> make porting things to FreeBSD a pain...

I seem to recall that Peter's proposal was for a script that drove configure
for you so presumably you could either use the script, or ignore it and
./configure --with..... if you preferred.

If this were the case I don't see how anyone could object as long as it's
nice and portable and is easy to maintain.

Regards, Dave.

pgsql-hackers by date

Next:From: Luis AmigoDate: 2002-01-31 09:41:05
Subject: Re: inline is not ANSI C
Previous:From: Sean ChittendenDate: 2002-01-31 05:21:48
Subject: Re: Kerberos and fe-auth...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group