public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: Postgresql Hackers <[email protected]>
Subject: Re: Build farm
Date: Fri, 21 Nov 2003 14:39:39 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

Tom Lane wrote:

>
>I think the main value of a build farm is that we'd get nearly immediate
>feedback about the majority of simple porting problems.  Your previous
>arguments that it wouldn't smoke everything out are certainly valid ---
>but we wouldn't abandon the regression tests just because they don't
>find everything.  Immediate feedback is good because a patch can be
>fixed while it's still fresh in the author's mind.
>

Yes, I seem to recall seeing several instances of things like "you mean 
foonix version 97 1/2 has a bad frobnitz.h?" over the last 6 months. 
Having that caught early is exactly the advantage, I believe.

>
>I'm for it ...
>  
>

I'm working on it :-)

Regarding "make distcheck" that Peter suggested I use, unless I'm 
mistaken it carefully does its own configure, thus ignoring the 
configure options set in the original directory. Perhaps we need either 
to have the distcheck target pick up all the --with/--without and 
--enable/--disable options, or to have a similar target that does that.

Thoughts?

cheers

andrew

view thread (83+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Build farm
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox