Re: [PATCH] Output configuration status after ./configure run.
| От | Tom Lane |
|---|---|
| Тема | Re: [PATCH] Output configuration status after ./configure run. |
| Дата | |
| Msg-id | 16536.1265816354@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | [PATCH] Output configuration status after ./configure run. (Priit Laes <plaes@plaes.org>) |
| Ответы |
Re: [PATCH] Output configuration status after
./configure run.
|
| Список | pgsql-hackers |
Priit Laes <plaes@plaes.org> writes:
> This patch enables showing configure status at the end of ./configure
> run and thus makes ./configure process a bit easier to follow (in the
> sense of what features are actually enabled).
I don't think anybody actually reads configure's output anyway, so I'm
not sure about the point of this. Usually you wish you knew this
information long afterwards. We do have tools (pg_config,
pg_controldata) for extracting such information from an existing
installation, which is the real use-case IMHO.
Also, it's quite unclear which items deserve a place in the list.
If it's just to repeat what was in the configure command-line, what
is the value of that?
regards, tom lane
В списке pgsql-hackers по дате отправления: