From owner-freebsd-ports  Wed Aug 16 04:05:45 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA19078
          for ports-outgoing; Wed, 16 Aug 1995 04:05:45 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA19071
          for <ports@freebsd.org>; Wed, 16 Aug 1995 04:05:42 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id EAA20841; Wed, 16 Aug 1995 04:05:42 -0700
Date: Wed, 16 Aug 1995 04:05:42 -0700
Message-Id: <199508161105.EAA20841@silvia.HIP.Berkeley.EDU>
To: jmacd@freefall.FreeBSD.org
CC: ports@freebsd.org
In-reply-to: <199508160942.CAA17128@freefall.FreeBSD.org> (message from Joshua Peck Macdonald on Wed, 16 Aug 1995 02:42:05 -0700)
Subject: Re: do not try the tcl-7.4 port!
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: ports-owner@freebsd.org
Precedence: bulk

(Sorry, forgot to CC: ports...ignore the first one, Josh)

 * I don't think you should bother trying to make the two compatible.  
 * People who are worried about having the latest version will install
 * it, people who are using the more common version will use it, I understand
 * it presents problems for your trying to compile everything and install 
 * everything and the dependencies issue, but really there are few reasons for
 * someone to have both sets of libraries around.  the people using tk4.0 and 
 * tcl7.4 are probably writing thier own applications, the people using tk3.6
 * and tcl7.3 are probably using other peoples applications.

There are lots of tcl-7.3/tk-3.6 stuff around, I don't think people
would want to throw them away (yet).  Maybe compilation is not an
issue except for a few (including us), but running is.

Also, don't forget the original install rule calls the libraries
"libtcl7.3.a" and "libtk4.0.a", and the script directory in
/usr/local/lib "tcl7.4" and "tk4.0".  John Ousterhout is definitely
intending them to coexist on the same machine, and make it possible to
compile applications for both the old and new versions.

We can still change it now, it's only the shared library name.  But it
will be too late after we ship a horde of tcl-7.4/tk-4.0 packages.

 * As I understand it, there is less of a compatibility problem between the two
 * tcl libraries anyways.  is the 7.3 -> 7.4 upgrade really breaking things?

Yes, I just had my zircon (dpwish) dump core on me.  It ran fine after 
I renamed the tcl-7.4 shared library.

Satoshi