From owner-freebsd-ports Wed Jun 25 12:21:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09907 for ports-outgoing; Wed, 25 Jun 1997 12:21:00 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09898 for ; Wed, 25 Jun 1997 12:20:57 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/) with SMTP id PAA21161; Wed, 25 Jun 1997 15:20:54 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id PAA15870; Wed, 25 Jun 1997 15:20:50 -0400 Date: Wed, 25 Jun 1997 15:20:22 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Tim Vanderhoek cc: Satoshi Asami , FreeBSD-Ports@FreeBSD.ORG Subject: Re: tcl In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Jun 1997, Tim Vanderhoek wrote: > On Tue, 24 Jun 1997, Satoshi Asami wrote: > > > Also, the main reason for this was to ease the transition from one > > version to another. Maybe for a hacker like you it doesn't matter, > > but for users who don't know how to hack ports to use whatever version > > they have, this is the only way to get ports that require different > > base tcl/tk to peacefully coexist. > > Well, perhaps Chuck is volunteering to go through all the ports > and patch them so that they'll work with v7.5, 7.6, or 8.0, > whichever happens to be on the installer's machine... :-) Understand that lots of tcl stuff will only work with a certain level of tcl libs, and not below that level, but, yes, I think that would be far more prefereable. Many people are not aware, I think, of the files tclConfig.sh and tkConfig.sh that tcl/tk normally installs in /usr/local/lib just for that purpose. Most of our tcl ports have been jiggered just to ignore those, or patch around them. I don't think that they will be much porting of new tcl things to FreeBSD until we stop getting in the way of tcl's own portability. I ended up nuking my own itcl port, because itcl wants to replace the normal tcl/tk (whatever you have) and replace it with it's own patched version, and since that unalterably killed this philosophy that folks must be able to run multiple tcl versions, itcl was killed. It wasn't a question of itcl not working, or the port not working; it was a question of being able to force it into our mold here. I don't like the mold much. I've discussed this enough, I don't think I'm enough in the majority to force this, so let this thread go away, please. Maybe a year from now I'll try again. > > > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------