From owner-freebsd-current  Wed Jan  7 18:56:46 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA15405
          for current-outgoing; Wed, 7 Jan 1998 18:56:46 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from silvia.HIP.Berkeley.EDU (ala-ca34-30.ix.netcom.com [207.93.143.158])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA15190;
          Wed, 7 Jan 1998 18:55:53 -0800 (PST)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id QAA16952; Wed, 7 Jan 1998 16:57:55 -0800 (PST)
Date: Wed, 7 Jan 1998 16:57:55 -0800 (PST)
Message-Id: <199801080057.QAA16952@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: ache@nagual.pp.ru, ports@freebsd.org, current@freebsd.org, jkh@freebsd.org
In-reply-to: <14910.884220576@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: tk80 port or tcl installation are broken on -current
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * Why?  It seems that things were fine until you rocked the boat with
 * a bsd.port.mk that tried to be too clever at detecting this. :)

Um, did you read the message?  That has nothing to do with my change,
Jordan.

In fact, the latest change was designed to prevent situations exactly
like this.

Satoshi