| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Priit Laes <plaes(at)plaes(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] Output configuration status after ./configure run. |
| Date: | 2010-02-10 20:30:22 |
| Message-ID: | 20100210203022.GT4922@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | daveg | 2010-02-10 21:08:58 | Re: TCP keepalive support for libpq |
| Previous Message | Euler Taveira de Oliveira | 2010-02-10 20:25:47 | Re: [PATCH] Output configuration status after ./configure run. |