Re: [PATCH] Output configuration status after ./configure run. - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] Output configuration status after ./configure run.
Date
Msg-id 20100210203022.GT4922@alvh.no-ip.org
Whole thread Raw
In response to Re: [PATCH] Output configuration status after ./configure run.  (Euler Taveira de Oliveira <euler@timbira.com>)
Responses Re: [PATCH] Output configuration status after ./configure run.
List pgsql-hackers
Euler Taveira de Oliveira escribió:
> Alvaro Herrera escreveu:
> > The general idea seems sensible to me.  I can't comment on the
> > specifics.
> > 
> +1. A lot of other programs have this summary at the end of configure
> execution. The problem is that PostgreSQL has too many options. Do we want to
> list all of them?

Maybe not all, but my bike is colored PGPORT, and this shed doesn't seem
to have anything that combines with that.

If this doesn't fit in 24x80 maybe we need to find a more compact way to
display things.

BTW if this thing is reasonably complete, we could have buildfarm
display this output in a summary page for each animal.  Seems more
readable than configure options.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Euler Taveira de Oliveira
Date:
Subject: Re: [PATCH] Output configuration status after ./configure run.
Next
From: daveg
Date:
Subject: Re: TCP keepalive support for libpq