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

From Robert Haas
Subject Re: [PATCH] Output configuration status after ./configure run.
Date
Msg-id 603c8f071002101335i2a99d50eo5b15b685d59d4022@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Output configuration status after ./configure run.  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [PATCH] Output configuration status after ./configure run.
List pgsql-hackers
On Wed, Feb 10, 2010 at 3:30 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> 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.

Well said, sir.

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

+1.  I wouldn't mind a one-line summary, but a two page summary seems
like a lot.

...Robert


pgsql-hackers by date:

Previous
From: daveg
Date:
Subject: Re: TCP keepalive support for libpq
Next
From: Tom Lane
Date:
Subject: Re: Writeable CTEs and empty relations