Re: Changes to handling version numbers internally

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Changes to handling version numbers internally
Date: 2000-07-04 19:56:31
Message-ID: 28390.962740591@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker <scrappy(at)hub(dot)org> 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 has always done this.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-07-04 19:57:31 zlib for pg_dump
Previous Message Tom Lane 2000-07-04 19:52:30 Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection