From owner-freebsd-current Thu May 1 15:03:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20263 for current-outgoing; Thu, 1 May 1997 15:03:37 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20255 for ; Thu, 1 May 1997 15:03:33 -0700 (PDT) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id RAA27172; Thu, 1 May 1997 17:03:13 -0500 (CDT) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <199705012106.HAA25766@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 1 May 1997 16:58:13 -0500 To: Bruce Evans From: Richard Wackerbarth Subject: Re: -current build is now broken.. Cc: jkh@time.cdrom.com, current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>And yes, it's possible for the older *.mk files on the host to screw >>you up, but that *also has to be taken into account* in any changes >>folks may make to the build structure since almost all of the 3.0 >>release/snap builds will be taking place on 2.2 systems for some time >>to come. You've no choice but to install 2.2 *.mk files on the first >>pass and, if this becomes a problem as the result of some change, then > >No, it's the responsibility of release/Makefile to be almost independent >of the host. I agree. In fact, this is the motive behind my desire to redo the make system. THE ENTIRE BUILD PROCEDURE SHOULD BE INDEPENDENT OF, AND NOT CONFLICT WITH THE UNDERLYING HOST. Unfortunately, when I really had time to work on this, I was "shot down". Now that I really no longer have time for FreeBSD, others are finally beginning to "see the light". :-(