Re: Changes to handling version numbers internally

you guys missed the key part of my message "if I were to remove all
sources but decide later ..." :)  if I remove sources, I no longer have
config-status to work with :)

On Wed, 5 Jul 2000, Peter Eisentraut wrote:

> 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
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org