From owner-freebsd-ports  Sun Aug  3 13:51:44 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA16476
          for ports-outgoing; Sun, 3 Aug 1997 13:51:44 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA16462;
          Sun, 3 Aug 1997 13:51:41 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id NAA03729; Sun, 3 Aug 1997 13:50:52 -0700 (PDT)
To: "Pedro Giffuni S," <pgiffuni@fps.biblos.unal.edu.co>
cc: Andreas Klemm <andreas@klemm.gtn.com>, phk@FreeBSD.ORG, ports@FreeBSD.ORG
Subject: Re: Current is currently really a mess (was: Re: Tk/Tcl broken(?)) 
In-reply-to: Your message of "Sun, 03 Aug 1997 15:34:58 PDT."
             <33E50792.6E94@fps.biblos.unal.edu.co> 
Date: Sun, 03 Aug 1997 13:50:52 -0700
Message-ID: <3725.870641452@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Perhaps I'm wrong, but I don't understand what is so mission-critical in
> Tcl as to decide to break the ports tree.

That's only the issue of the day.  My point was that there would
always be something if -current fulfils its original mandate of being
a testing ground.  TCL is just the cause du-jour, it's not the truly
fundamental problem we're facing here.

						Jordan