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

In response to

• Re: Changes to handling version numbers internally at 2000-07-04 17:40:32 from The Hermit Hacker

Responses

• Re: Changes to handling version numbers internally at 2000-07-05 22:31:02 from The Hermit Hacker

pgsql-hackers by date

Next:	From: Peter Eisentraut	Date: 2000-07-05 00:12:35
	Subject: Repair plan for inet and cidr types
Previous:	From: Peter Eisentraut	Date: 2000-07-05 00:12:15
	Subject: Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)