From owner-freebsd-ports  Sun Jul 30 19:17:15 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id TAA01879
          for ports-outgoing; Sun, 30 Jul 1995 19:17:15 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id TAA01873
          for <ports@freebsd.org>; Sun, 30 Jul 1995 19:17:12 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id TAA02682; Sun, 30 Jul 1995 19:17:04 -0700
Date: Sun, 30 Jul 1995 19:17:04 -0700
Message-Id: <199507310217.TAA02682@silvia.HIP.Berkeley.EDU>
To: kelly@fsl.noaa.gov
CC: msmith@atrad.adelaide.edu.au, ports@freebsd.org
In-reply-to: <9507310212.AA15021@emu.fsl.noaa.gov> (kelly@fsl.noaa.gov)
Subject: Re: Tcl 7.4 / Tk 4.0 Ports
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: ports-owner@freebsd.org
Precedence: bulk

 *     Satoshi> Ok, seems like it's too dangerous to lose tcl-7.3, and we
 *     Satoshi> definitely can't erase tk-3.6.  Now, what should we do?

 * At least the out-of-the-box install for both tcl7.4 and tk4.0 don't
 * clobber exiting files.  Ousterhout's added version numbers to the
 * names of the directories, the libraries, and the executables.

Oops sorry, I was talking about our ports tree, not the users'
/usr/local filesystem (but that's another concern that I was going to
take a closer look after we decide where to put them in our ports
tree).

Good to know they designed it that way, though.  Thanks. :)

Satoshi