From owner-freebsd-bugs Thu Jan 16 21:55:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA12286 for bugs-outgoing; Thu, 16 Jan 1997 21:55:23 -0800 (PST) Received: from squirrel.tgsoft.com (squirrel.tgsoft.com [207.167.64.183]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA12279 for ; Thu, 16 Jan 1997 21:55:20 -0800 (PST) Received: (from thompson@localhost) by squirrel.tgsoft.com (8.8.3/8.6.12) id VAA26548; Thu, 16 Jan 1997 21:55:39 -0800 (PST) Date: Thu, 16 Jan 1997 21:55:39 -0800 (PST) Message-Id: <199701170555.VAA26548@squirrel.tgsoft.com> From: mark thompson To: joerg_wunsch@uriah.heep.sax.de CC: jkh@time.cdrom.com, freebsd-bugs@freefall.freebsd.org In-reply-to: Subject: Re: bin/2493: make $DESTDIR work Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Date: Thu, 16 Jan 1997 21:54:30 +0100 From: j@uriah.heep.sax.de (J Wunsch) Cc: jkh@time.cdrom.com, freebsd-bugs@freefall.freebsd.org As mark thompson wrote: Well, i've only heard one objection, that was: ``Name this thing TARGETDIR.'' What about this? Could do that... There are a few existing occurances of -I${DESTDIR}/usr/include, which i am now given to understand are "not really correct", and should presumably come to be -I${TARGETDIR}/usr/include? I would kindly ask you to also do one final test: run a ``make release'' (i hope you've got the disk space and the CVS tree for this). This is one of the occasions where ${DESTDIR} is exploitet regularly (perhaps the only occasion in the entire FreeBSD tree). If your changes broke the existing ${DESTDIR} behaviour, this should pop up there. If it doesn't break anything, i see no reason to not include it. Ok. If i change it to find everything in TARGETDIR, that should eliminate some of the concerns with DESTDIR, no? -mark