Re: Changes to handling version numbers internally
От | Peter Eisentraut |
---|---|
Тема | Re: Changes to handling version numbers internally |
Дата | |
Msg-id | Pine.LNX.4.21.0007042335000.3542-100000@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Changes to handling version numbers internally (The Hermit Hacker <scrappy@hub.org>) |
Ответы |
Re: Changes to handling version numbers internally
|
Список | pgsql-hackers |
The Hermit Hacker writes: > One thought, and with all your recent changes you may have done this, but > is there any way of putting some sort of text file as part of the install > procedure that "stores" the ./configure command line? Something that, if > I were to remove all sources but decide later that I want to add, let's > say, multi-byte, I could do 'cat ~pgsql/CONFIGURE' to find out how the > system is already compiled? config.status stores the current configuration. To reuse it, run `./config.status --recheck'. If you just want to *know* what the current configuration is, then `head config.status' should answer that pretty well. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
В списке pgsql-hackers по дате отправления: