Skip site navigation (1) Skip section navigation (2)

Re: Changes to handling version numbers internally

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 (view raw, whole thread or download thread mbox)
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

Peter Eisentraut                  Sernanders väg 10:115
peter_e(at)gmx(dot)net                   75262 Uppsala            Sweden

In response to


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group