Re: [HACKERS] Next release is 7.0(?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: Brook Milligan <brook(at)biology(dot)nmsu(dot)edu>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Next release is 7.0(?)
Date: 1999-10-11 18:57:25
Message-ID: 8663.939668245@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
>> Would this also be a relevant time to get a regression test to run on
>> a non-installed system?

> Gee, I never even though of that. What advantage would there be for
> that?

It has been suggested before, and I think it's a good idea. The
advantage is you can smoke-test a new compilation *before* you blow
away your existing installation ;-)

It is, of course, possible to do that by installing into a nonstandard
location/port and then running the regress tests there. But you have
to know exactly what you're doing to do that. If we're going to
overhaul install, we should make it easier to run the regress tests
that way, or even better with not-installed-at-all binaries from the
source tree.

Another thing I'd like to see would be full support for building in
a separate object-directory tree, leaving the source tree pristine
rather than filled with configure and build output files.
This is a standard GNU practice and I think it's a good one.

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-10-11 19:07:46 Re: Scan by TID (was RE: [HACKERS] How to add a new build-in operator)
Previous Message Lamar Owen 1999-10-11 18:32:26 Re: [HACKERS] Next release is 7.0(?)