From owner-freebsd-current Fri May 2 16:39:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00490 for current-outgoing; Fri, 2 May 1997 16:39:44 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00485 for ; Fri, 2 May 1997 16:39:42 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id QAA24331; Fri, 2 May 1997 16:39:29 -0700 (PDT) Message-Id: <199705022339.QAA24331@austin.polstra.com> To: John Hay cc: current@FreeBSD.ORG Subject: Re: -current build is now broken.. In-reply-to: Your message of "Sat, 03 May 1997 00:35:27 +0200." <199705022235.AAA26971@zibbi.mikom.csir.co.za> References: <199705022235.AAA26971@zibbi.mikom.csir.co.za> Date: Fri, 02 May 1997 16:39:28 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I think with a little care it will be possible to keep building > 3.0 snaps and releases on a 2.2 machine. Have you forgotten how this thread got started? The thing that you say will be possible "with a little care" got broken by Bruce. Nobody on this project is more careful than Bruce. (And his competence is hardly in doubt, either.) A little care doesn't cut it in software -- you need testing. It's unreasonable to expect all the developers to have what's needed for testing 3.0 release builds on 2.2 machines. It's much more reasonable to ask that the people who build releases -- a dramatically smaller group -- do it on up-to-date systems. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth