From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-docs@lists.postgresql.org
Subject: Can we bring some organization to the configure options list?
Date: Fri, 07 Jun 2019 10:22:49 -0400
Message-ID: <6384.1559917369@sss.pgh.pa.us> (raw)
I was just noticing, while answering a user question, the amount of
unorganized urban sprawl we've accumulated in
https://www.postgresql.org/docs/devel/install-procedure.html
We've got practically-essential options like --prefix and
--with-openssl intermixed with obscure portability flags
and options that only developers should take any interest in.
For bonus points, the ordering seems chosen largely by dartboard;
there's certainly no visible plan to it.
I think we should try to improve the situation by dividing the
configure options into categories and/or separating commonly
used options from obscure ones. I don't have any concrete
proposal to make right now, but I am hoping to kick off a
discussion about what such an organization would look like.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-docs@lists.postgresql.org
Subject: Re: Can we bring some organization to the configure options list?
In-Reply-To: <6384.1559917369@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox