From owner-freebsd-current Tue Jun 25 15:55:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04679 for current-outgoing; Tue, 25 Jun 1996 15:55:40 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA04670 for ; Tue, 25 Jun 1996 15:55:34 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA00779; Tue, 25 Jun 1996 16:54:58 -0600 (MDT) Date: Tue, 25 Jun 1996 16:54:58 -0600 (MDT) Message-Id: <199606252254.QAA00779@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: Bruce Evans , freebsd-current@freebsd.org, nate@sri.MT.net Subject: Re: Building inside of /usr/src? In-Reply-To: <18586.835718568@time.cdrom.com> References: <199606250826.SAA31406@godzilla.zeta.org.au> <18586.835718568@time.cdrom.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Sorry Bruce, but there's nothing broken here except your expectation > that everything should be still broken in the ways it was broken > before! :-) The *previous* behavior *allowed* you to use a read-only /usr/src tree, but it wasn't it's primary purpose. As a matter of fact (as I already pointed out to someone else), BSDi uses the same setup as we used to have on the CD which allowed building from a Read-Only media, but they simply pre-created the symlinks before the burned the CDs. (At least this was on an older CD of theirs, I haven't looked in quite a while). As I understand it, the purpose of the obj stuff was to allow building multiple architectures in one tree, and the symlink/'/usr/obj' was a way to keep *all* of the build files in one area. However, you could use obj directories just as easily (the previous version of bsd.obj.mk allowed this, but this was removed). You're removed some *useful* functionality from the obj system that both Bruce and I both pointed out, and your arguements haven't even begun to address the *real* issue. Instead, you've hid behind the smoke-screen of 'this is how it was *supposed* to work'. I disagree. The folks at CSRG were fully capable of making the obj stuff 'less flexible' as you've done, but instead left it flexible. Having a 'read-only' source tree is a side-effect of wanting to guarantee that none of the architecture-specific stuff inside the source tree to avoid screwing up the next architecture's build. Read-only sources wasn't the primary reason for 'obj'. Enough said. It's not a religious issue for me, but I do wish we could have the flexibility of the 'old' way and a knob to turn on the new behavior for those times where building from a read-only media is desired. Nate