From owner-freebsd-ports  Fri Jan  3 04:06:09 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id EAA15792
          for ports-outgoing; Fri, 3 Jan 1997 04:06:09 -0800 (PST)
Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA15786
          for <ports@freebsd.org>; Fri, 3 Jan 1997 04:06:05 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (ala-ca9-50.ix.netcom.com [207.93.143.114]) by dfw-ix10.ix.netcom.com (8.6.13/8.6.12) with ESMTP id EAA26006; Fri, 3 Jan 1997 04:05:26 -0800
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id EAA01500; Fri, 3 Jan 1997 04:05:22 -0800 (PST)
Date: Fri, 3 Jan 1997 04:05:22 -0800 (PST)
Message-Id: <199701031205.EAA01500@silvia.HIP.Berkeley.EDU>
To: peter@spinner.DIALix.COM
CC: ports@freebsd.org
Subject: TK_BUILD_LIB_SPEC in tkConfig.sh
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

TK_BUILD_LIB_SPEC uses the "real" directory instead of the "canonical"
directory, can we make it to use "/usr/ports"?  Otherwise the packages
are going to point to some high heaven (/usr/ports are symlinks on all
our build machines).

Of course this is going to cause problems if ${PORTSDIR} is set on the
user's system.  OK, can you make it substitute ${PORTSDIR} instead,
and I'll try to make sure I don't set ${PORTSDIR} to anything other
than /usr/ports when I build a package.

Bleah.  This is totally rotten.  Just how can one justify leaving a
reference to a (possibly) private directory in a public file.  I hate
tcl/tk. :(

Satoshi