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

From Tom Lane
Subject Re: [PATCH] Output configuration status after ./configure run.
Date
Msg-id 22546.1265854672@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Output configuration status after ./configure run.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] Output configuration status after ./configure run.  (Robert Haas <robertmhaas@gmail.com>)
Re: [PATCH] Output configuration status after ./configure run.  (Euler Taveira de Oliveira <euler@timbira.com>)
Re: [PATCH] Output configuration status after ./configure run.  (Priit Laes <plaes@plaes.org>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Feb 10, 2010 at 3:30 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
>> 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.

So it seems there's some consensus that:

1. This printout should display everything configurable from a configure
option, and nothing else (ie, not any of the platform-dependent
conclusions that configure draws).

2. The printout has to be made to fit in 24x80 or so.

I'm still quite dubious about the usefulness, but I could live with this
if someone explains to me how the printout is going to stay within 24x80
given the inevitable growth in number of configure options ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres Triggers issue
Next
From: Andres Freund
Date:
Subject: Re: Re: Faster CREATE DATABASE by delaying fsync (was 8.4.1 ubuntu karmic slow createdb)