From owner-freebsd-current  Tue Aug  5 01:02:04 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA28053
          for current-outgoing; Tue, 5 Aug 1997 01:02:04 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca8-36.ix.netcom.com [207.93.141.164])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA28046
          for <current@FreeBSD.ORG>; Tue, 5 Aug 1997 01:01:58 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id BAA15890; Tue, 5 Aug 1997 01:01:50 -0700 (PDT)
Date: Tue, 5 Aug 1997 01:01:50 -0700 (PDT)
Message-Id: <199708050801.BAA15890@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: andreas@klemm.gtn.com, current@FreeBSD.ORG
In-reply-to: <2920.870634837@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: Make this a relese coordinator decision (was Re: ports-current/packages-current discontinued)
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * To put it another way, if something as minor as a new version of TCL
 * going in screws up the ports collection this badly then we've already

The problem is not whether a new version of tcl is "minor" or "major", 
Jordan.  The problem is that many ports rely on the internals, and
there is no easy way to make those ports work independently of tcl
versions.

On the other hand, the normal -current irregularities (Garrett's
network header works, for instance), while it may break a lot of ports 
at first, are very easy to fix because it's just a simple "#if" job
just repeated N times or N ports.

Satoshi