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

From Alvaro Herrera
Subject Re: [PATCH] Output configuration status after ./configure run.
Date
Msg-id 20100211161742.GA3145@alvh.no-ip.org
Whole thread Raw
In response to Re: [PATCH] Output configuration status after ./configure run.  (Euler Taveira de Oliveira <euler@timbira.com>)
List pgsql-hackers
Euler Taveira de Oliveira escribió:
> Tom Lane escreveu:
> > 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 ...
> > 
> AFAICS, we have > 40 configure options. If we want this to fit in 24 rows (i)
> we should choose popular options or (ii) print only features/packages that
> have a non-default option/value.

Or (iii) display more than one per line, for example
Configured PL languages: Perl Python TclConfigued block sizes: WAL: 8192    data: 8192    sth else: 16384

There you have six configure options in two lines.

> Both ideas aren't ideal for machine-readable
> format (as someone mentioned pgbuildfarm) because the summary is partial

My idea regarding buildfarm was to have it for human consumption, not
machine readable.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Avoiding bad prepared-statement plans.
Next
From: Tom Lane
Date:
Subject: Re: Hostnames in pg_hba.conf