Re: [PATCH] Output configuration status after ./configure run.
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Euler Taveira de Oliveira <euler@timbira.com>, Priit Laes <plaes@plaes.org>, pgsql-hackers@postgresql.org
Date: 2010-02-11T03:02:12Z
Lists: pgsql-hackers
On Wed, Feb 10, 2010 at 9:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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 ... I'm dubious too. I'm +1 for shorter, but neutral on the idea in general. ...Robert