From owner-freebsd-ports Tue Jun 24 15:55:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA12097 for ports-outgoing; Tue, 24 Jun 1997 15:55:27 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA12086 for ; Tue, 24 Jun 1997 15:55:22 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.5/8.7.3) id PAA14518; Tue, 24 Jun 1997 15:54:34 -0700 (PDT) Date: Tue, 24 Jun 1997 15:54:34 -0700 (PDT) Message-Id: <199706242254.PAA14518@vader.cs.berkeley.edu> To: chuckr@glue.umd.edu CC: FreeBSD-Ports@freebsd.org In-reply-to: (message from Chuck Robey on Tue, 24 Jun 1997 18:38:56 -0400 (EDT)) Subject: Re: tcl From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Well, I was thinking about all the stuff done to allow different versions * of tcl and tk to coexist. In my opinion, they break the method that * tcl/tk uses to determine things itself. Yes, but that doesn't have anything to do with a certain version of tcl being in /usr. With tcl-7.5/7.6 and tk-4.1/4.2 as well as their Japanese counterparts, we'll still have the same problem. (Is 8.0 out of alpha yet?) * I agree, tk wouldn't be added. I'd be happy yanking tcl out of the * sources. I guess I just didn't want to crosspost on this, yet. I might * bring it up on hackers, later. I don't think there are any scripts in tcl * that couldn't be in perl. No comment on that from me. ;) Satoshi