| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Changes to handling version numbers internally |
| Date: | 2000-07-05 00:12:24 |
| Message-ID: | Pine.LNX.4.21.0007042335000.3542-100000@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-07-05 00:12:35 | Repair plan for inet and cidr types |
| Previous Message | Peter Eisentraut | 2000-07-05 00:12:15 | Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary) |