From owner-freebsd-ports  Sat Jan 18 17:57:07 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id RAA12201
          for ports-outgoing; Sat, 18 Jan 1997 17:57:07 -0800 (PST)
Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA12162;
          Sat, 18 Jan 1997 17:56:56 -0800 (PST)
Received: from baloon.mimi.com (sjx-ca55-01.ix.netcom.com [206.214.106.97]) by dfw-ix2.ix.netcom.com (8.6.13/8.6.12) with ESMTP id RAA13189; Sat, 18 Jan 1997 17:56:15 -0800
Received: (from asami@localhost) by baloon.mimi.com (8.8.4/8.6.12) id RAA19321; Sat, 18 Jan 1997 17:56:08 -0800 (PST)
Date: Sat, 18 Jan 1997 17:56:08 -0800 (PST)
Message-Id: <199701190156.RAA19321@baloon.mimi.com>
To: chuckr@glue.umd.edu
CC: ports@freebsd.org, committers@freebsd.org, ports-jp@jp.freebsd.org
In-reply-to: <Pine.OSF.3.95.970118203515.27246C-100000@professor.eng.umd.edu> (message from Chuck Robey on Sat, 18 Jan 1997 20:41:49 -0500 (EST))
Subject: Re: multiple versions of tcl/tk
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * > (tk.h and tkConfig.sh) in subdirectories so that ports that require a
               ^^^^^^^^^^^

 * This is a problem, Satoshi.  The file involved is tkConfig.sh.  It's the
 * one that all the other ports query for all their information, before
 * they're installed (during their build).  It's really the key one, since
 * all the other hiding has to be announced inside that file.

I don't think it has anything about the include files though.  (It
only has "root of platform-indepent files" (i.e., /usr/local).

 * Ports look for it now in /usr/local/lib or /usr/local/include.  If you
 * want to do what you're talking about above, I would guess that the right
 * thing to do *might be* to hide multiple copies of the tkConfig.sh file
 * (for whatever version is involved) inside your version-specific hierarchy,
 * and take the hit on extra work configuring new tcl/tk applications.  This
 * means breaking all the automatic configurations for stuff that people put
 * in their machines *other than* stuff coming from our ports method.
 * 
 * Is this what you want to do?

Yes, that was what I meant (see ^^^^ above).  Sorry if I wasn't clear.
To leave no ambiguity this time, here are the two symlinks I intend to 
create:

/usr/local/include/tk.h -> tk4.1/generic/tk.h
/usr/local/lib/tkConfig.sh -> tk4.1/tkConfig.sh

for non-default (i.e., not 4.1) versions, the files will move but the
symlinks won't be created.

Satoshi