From owner-freebsd-current Sun Aug 3 21:05:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10836 for current-outgoing; Sun, 3 Aug 1997 21:05:52 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10826 for ; Sun, 3 Aug 1997 21:05:46 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA26303; Sun, 3 Aug 1997 22:05:37 -0600 (MDT) Date: Sun, 3 Aug 1997 22:05:37 -0600 (MDT) Message-Id: <199708040405.WAA26303@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: David Nugent , current@freebsd.org Subject: Re: ports-current/packages-current discontinued In-Reply-To: <17153.870568174@time.cdrom.com> References: <199708022133.HAA14498@unique.usn.blaze.net.au> <17153.870568174@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Yes yes yes, we know all this. But by that same token, and what you > slain, be that particular giant perl or TCL. In reality, they're > simply symptoms of a greater maliase Agreed, but further 'bloating' of the systems isn't the way to solve the problem. "If we continue to annoy them enough, they'll be some angry a solution will simply pop into our laps." Nate