From owner-freebsd-current Mon Aug 4 06:51:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA01500 for current-outgoing; Mon, 4 Aug 1997 06:51:54 -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 GAA01495 for ; Mon, 4 Aug 1997 06:51:52 -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 GAA00746; Mon, 4 Aug 1997 06:51:26 -0700 (PDT) To: Wolfgang Helbig cc: current@FreeBSD.ORG Subject: Re: Current is currently really a mess (was: Re: Tk/Tcl broken(?)) In-reply-to: Your message of "Mon, 04 Aug 1997 00:43:04 +0200." <199708032243.AAA01485@helbig.informatik.ba-stuttgart.de> Date: Mon, 04 Aug 1997 06:51:25 -0700 Message-ID: <742.870702685@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The one and only reason for any OS is to support applications, > which in FreeBSD means to a great extent the applications of the > ports collection. I agree, and that's why I've always felt that dropping support for ports in our current release branch was a big mistake. Much of the user base agreed and wondered why -current got all the new toys while they were left to stagnate, told on one hand to avoid current due to instability or lack of testing and then told on the other that they couldn't have all the nifty new ports because that was purely a -current feature. It also still comes as something of a shock to me that many of the people in this discussion who have been vehemently defending the idea of maintaining a -current ports collection also go strangely silent when this point is brought up. I guess that when it comes right down to it, developers will always defend their interests first but I'd hoped we might at least be a little less *obvious* about that. :) Jordan