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 603c8f071002101127m6ff1626fobe4704f8e6ac68df@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Output configuration status after ./configure run.  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Wed, Feb 10, 2010 at 2:16 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Maybe you didn't type it, but it came from elsewhere?  Maybe you're
> inheriting settings from some environment variable, or a file?  Maybe
> you're eval'ing pg_config --configure?

Yeah, could be.

> The general idea seems sensible to me.  I can't comment on the
> specifics.

I took a quick look at it.  It's basically just a block of output at
the end of configure that reflects the values for a subset of the
configuration parameters (for example, just off the top of my head,
--enable-debug, --enable-casserts, --enable-depend, and --enable-nls
aren't there).  It already won't fit in a 24x80 window, and if we
actually make it complete, it'll be considerably longer.  While not
denying its possible usefulness to the OP, I'm not sure that in
general more people would find it useful than annoying.  I might be
wrong, though.

...Robert


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] Output configuration status after ./configure run.
Next
From: Teodor Sigaev
Date:
Subject: Re: [CFReview] Red-Black Tree