Re: [PATCH] Output configuration status after ./configure run.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(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-11 02:17:52
Message-ID: 22546.1265854672@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Feb 10, 2010 at 3:30 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2010-02-11 02:27:30 Re: [HACKERS] Re: Faster CREATE DATABASE by delaying fsync (was 8.4.1 ubuntu karmic slow createdb)
Previous Message Tom Lane 2010-02-11 02:10:11 Re: Postgres Triggers issue