From owner-freebsd-current Fri May 2 17:01:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA01335 for current-outgoing; Fri, 2 May 1997 17:01:59 -0700 (PDT) Received: from news.quick.net (donegan@news.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA01328 for ; Fri, 2 May 1997 17:01:57 -0700 (PDT) Received: (from donegan@localhost) by news.quick.net (8.8.5/8.6.9) id RAA18660; Fri, 2 May 1997 17:01:25 -0700 (PDT) Date: Fri, 2 May 1997 17:01:25 -0700 (PDT) From: "Steven P. Donegan" To: John Hay cc: John Polstra , current@FreeBSD.ORG Subject: Re: -current build is now broken.. In-Reply-To: <199705022235.AAA26971@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 3 May 1997, John Hay wrote: > > 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 > John, where I work if you bring up a 'problem' or 'issue' guess what - you own it. So, if you want to be able to build non-congruent releases (early on late or vice-versa) then go ahead and take a whack at making it possible. Fading back to lurker status again... Steven P. Donegan donegan@quick.net