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

Ühel kenal päeval, K, 2010-02-10 kell 21:17, kirjutas Tom Lane:
> 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).

Do you mean also CC, CFLAGS, PREFIX, etc?

> 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 a bit reluctant to 24x80 requirement. Without this patch one has to
scroll a lot more backlog from ./configure (hundreds of lines) to see
what changes really applied and also the output is a bit more cryptic.
The same goes to ./configure --help. And I don't really know any other
ways...

And besides, this "feature" only matters for people who play with the
source. Everyone else is already using either binary packages or build
systems (like portage).

Also:
> Hmm. That implies that you didn't look at the command that you typed
> but you did look at its output. I'm not going to say "no one does
> that" (who am I to judge?) but it seems kind of strange to me.

Yes, strange but I don't really make the connection of blindly typing
the command and figuring out what options configure supports... :S