From owner-freebsd-ports  Wed Mar 18 21:29:37 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA20047
          for freebsd-ports-outgoing; Wed, 18 Mar 1998 21:29:37 -0800 (PST)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20035
          for <freebsd-ports@FreeBSD.ORG>; Wed, 18 Mar 1998 21:29:35 -0800 (PST)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: from bubble.didi.com (cs11i41.ppp.infoweb.or.jp [202.219.190.201]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id VAA26707; Wed, 18 Mar 1998 21:29:23 -0800 (PST)
Received: (from asami@localhost)
	by bubble.didi.com (8.8.7/8.8.8) id OAA01265;
	Thu, 19 Mar 1998 14:26:39 +0900 (JST)
	(envelope-from asami)
Date: Thu, 19 Mar 1998 14:26:39 +0900 (JST)
Message-Id: <199803190526.OAA01265@bubble.didi.com>
To: kargl@troutmask.apl.washington.edu
CC: eivind@yes.no, freebsd-ports@FreeBSD.ORG
In-reply-to: <199803190318.TAA16903@troutmask.apl.washington.edu> (kargl@troutmask.apl.washington.edu)
Subject: Re: bsd.port.mk bug???
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

 * Suppose I have a program foobar, and the person who wrote foobar
 * decided to name a file tk.h.  Now, suppose I install foobar in /usr/local
 * and tk.h ends up in /usr/local/include.  Furthermore, foobar needs 
 * tk.h to run (it may contain config info).   Removing tk.h is not a 
 * good thing.

This is ridiculous.  What's going to happen if some port's configure
script finds it and thinks it's the tk header?

Steve, we have explored many possibilities before finalizing on the
current solution.  (No, we didn't actually consider adding an extra
variable to every port's Makefile that requires tcl or tk.  That's too
expensive, besides it doesn't help prevent the source of the biggest
headache, i.e., port submissions from people who have obsolete files
on their system.)

Please let's not waste any more time on this.  If you have a problem
with having to remove a couple of files so the whole system can stay
manageable and work for most of the users, then I'm sorry but the
ports system is not for you.

Satoshi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message