From owner-freebsd-current Fri May 2 15:36:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA27524 for current-outgoing; Fri, 2 May 1997 15:36:05 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA27511 for ; Fri, 2 May 1997 15:35:58 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id AAA26971; Sat, 3 May 1997 00:35:27 +0200 (SAT) From: John Hay Message-Id: <199705022235.AAA26971@zibbi.mikom.csir.co.za> Subject: Re: -current build is now broken.. In-Reply-To: <199705021554.IAA21290@austin.polstra.com> from John Polstra at "May 2, 97 08:54:10 am" To: jdp@polstra.com (John Polstra) Date: Sat, 3 May 1997 00:35:27 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In article <25335.862526471@time.cdrom.com>, > Jordan K. Hubbard wrote: > > Also, as I said, now that we're *bootstrapping* many 3.0 builds from > > 2.2 ones there are even more issues involved and, while I'd love to be > > able to say "chicken and egg, install a 3.0 machine to make 3.0 > > releases and simplify the makesfiles", I simply don't have the > > resources to have *both* 2.2 and 3.0 release building machines > > available at the moment (though it'd sure be nice) nor do, I believe, > > the other release engineers. That's another one of them-there > > "real-world constraints" I mentioned earlier. :-) > > I think it is reasonable to require that it be possible to bootstrap > a make world for 3.0 on a 2.2 machine. > > But I do not think it is reasonable to require that it be possible > to bootstrap a make _release_ for 3.0 on a 2.2 machine. > I don't think it is unreasonable to expect it. I have been building 2.2 and 2.2.1 releases on a 2.1.7 box here (because it is the only PPro box here). That box has been upgraded today to 2.2-stable but I would want to use it to build 3.0 snaps and releases. It can't run -current because it is also in use as our server. I think with a little care it will be possible to keep building 3.0 snaps and releases on a 2.2 machine. John -- John Hay -- John.Hay@mikom.csir.co.za