From owner-freebsd-bugs Tue Jan 14 21:52:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA09810 for bugs-outgoing; Tue, 14 Jan 1997 21:52:45 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA09803 for ; Tue, 14 Jan 1997 21:52:42 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id VAA21419; Tue, 14 Jan 1997 21:51:23 -0800 (PST) To: mark thompson cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/2493: make $DESTDIR work In-reply-to: Your message of "Tue, 14 Jan 1997 20:40:02 PST." <199701150440.UAA04014@freefall.freebsd.org> Date: Tue, 14 Jan 1997 21:51:23 -0800 Message-ID: <21415.853307483@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I believe that whether or not ${DESTDIR} was 'guaranteed' to do what i > want (allow you to do a make world without overwritting your running > system), 90% of the Makefiles are coded so you can do just that. The > changes that i submitted take you to between 95-99% of the way there and > *should not* break anything. I dunno, sounds convincing to me, Joerg. ;-) How much testing have you done with this, Mark? When you say *should not* is this from long-standing experience and much comparative testing of binaries (run mtree over tree A, then over tree B, compare results) or is this more of an engineer's standard "*I hope it won't*" :-) If it's the former, I certainly don't see a problem. I agree that there's no reason NOT to make DESTDIR a more capable instrument if it doesn't break any existing functionality. Jordan