From owner-freebsd-current Wed Nov 15 18:11:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA29014 for current-outgoing; Wed, 15 Nov 1995 18:08:45 -0800 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA29007 for ; Wed, 15 Nov 1995 18:08:42 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id SAA01076; Wed, 15 Nov 1995 18:08:23 -0800 Date: Wed, 15 Nov 1995 18:08:23 -0800 Message-Id: <199511160208.SAA01076@silvia.HIP.Berkeley.EDU> To: wosch@cs.tu-berlin.de CC: current@freebsd.org In-reply-to: <199510251635.RAA19353@localhost> (message from Wolfram Schneider on Wed, 25 Oct 1995 17:35:25 +0100) Subject: Re: absolute pathnames in /usr/share/mk/bsd.*.mk From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org Precedence: bulk (Old mail, quoted in full for context) * Date: Wed, 25 Oct 1995 17:35:25 +0100 * From: Wolfram Schneider * * * Some bsd.*.mk files use absolute pathnames, eg. /bin/rm or * /usr/sbin/pkg_create. * * I use FreeBSD 2.0A and install the pkg_create from 2.1 in * /usr/local/bin. This does not work because pkg_create was hard coded * as /usr/sbin/pkg_create in bsd.port.mk. Same for the new sed(1). * * In my opinion absolute pathnames should never used. * * * wosch@campa <17:22:18> [~/current/src/share/mk] 698 * $ for file in *.mk;do printf "%20s " $file;grep bin/ $file|wc;done|grep -v 0 * bsd.doc.mk 1 5 62 * bsd.info.mk 1 5 38 * bsd.kmod.mk 2 8 72 * bsd.port.mk 77 469 3887 * * Wolfram This is intentional, at least for bsd.port.mk. We have gotten lots of reports of bsd.port.mk failing because the user didn't have /usr/sbin or /sbin in the search path. I'm sorry it doesn't work for you, but we have to take care of the majority first.... ;< Satoshi