| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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-15 14:36:13 |
| Message-ID: | 1266244573.6163.2.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On ons, 2010-02-10 at 18:25 -0200, Euler Taveira de Oliveira wrote:
> 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?
The reason that a lot of other packages have this sort of display is
probably because they use an opportunistic configuration approach,
meaning they configure the packages with whatever libraries they happen
to find installed at the time. So you don't actually know what you are
getting until the end of the configure run. (Clearly, however, a
package autobuilder doesn't read that output, so the concept is broken.)
PostgreSQL doesn't work that way (for the most part).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2010-02-15 14:37:20 | ToDo: preload for fulltext dictionary |
| Previous Message | Robert Haas | 2010-02-15 14:29:36 | alpha4 timing (was: Speed up CREATE DATABASE) |