From owner-freebsd-current  Thu Oct 26 03:06:41 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id DAA29715
          for current-outgoing; Thu, 26 Oct 1995 03:06:41 -0700
Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA29675
          for <current@freebsd.org>; Thu, 26 Oct 1995 03:06:17 -0700
Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id KAA05263 for <current@freebsd.org>; Thu, 26 Oct 1995 10:34:22 +0100
Received: (from wosch@localhost) by localhost (8.6.9/8.6.9) id RAA19353; Wed, 25 Oct 1995 17:35:25 +0100
Date: Wed, 25 Oct 1995 17:35:25 +0100
From: Wolfram Schneider <wosch@cs.tu-berlin.de>
Message-Id: <199510251635.RAA19353@localhost>
To: current@freebsd.org
Subject: absolute pathnames in /usr/share/mk/bsd.*.mk
Reply-to: Wolfram Schneider <wosch@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-current@freebsd.org
Precedence: bulk


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