From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 06:29:16 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EEF2106566B; Tue, 27 Sep 2011 06:29:16 +0000 (UTC) (envelope-from ade@FreeBSD.org) Received: from panix.lovett.com (panix.lovett.com [166.84.7.128]) by mx1.freebsd.org (Postfix) with ESMTP id 15FB98FC13; Tue, 27 Sep 2011 06:29:15 +0000 (UTC) Received: from r74-192-180-219.htvlcmta01.hnvitx.tl.dh.suddenlink.net ([74.192.180.219] helo=lab.lovett.com) by panix.lovett.com with esmtpa (Exim 4.76 (FreeBSD)) (envelope-from ) id 1R8RAI-000BIi-N5; Tue, 27 Sep 2011 06:29:15 +0000 Date: Tue, 27 Sep 2011 01:29:02 -0500 From: Ade Lovett To: ports@freebsd.org, current@freebsd.org Message-ID: <20110927012902.2ebb4a3e@lab.lovett.com> In-Reply-To: References: <20110926230335.041fd9aa@lab.lovett.com> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: HEADS UP: ports/ and 10.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2011 06:29:16 -0000 > It just means that folks didn't plan ahead and didn't think up > proper contingency plans. First off, apologies to Garrett, I'm not picking on you directly, but I kinda knew this would come up. The undeniable fact is that configure scripts in general have chosen to do things a certain way. Unfortunately for us (us being FreeBSD), we have now broken these conceptions by moving to a dual-digit major release. Emails have been passed around (somewhere starting around the 7.x series when it became obvious we would be hitting 10.x a lot sooner than expected). It is no-one's fault that 23,000+ third party applications couldn't be tweaked prior to a trivial change in /sys/conf/newvers.sh that resulted in this "oops". The message I wanted to set across is that until such time as us ports folks have had a chance to really work out the damage, and start on fixing it, then for those running 10-CURRENT, things are likely to be non-linear for a while. Our primary responsibility right now is to ensure that a proper set of packages gets built for the impending 9.0-RELEASE. We haven't forgotten you bleeding edge folks, it's just that right now, you're somewhat down the food chain. Make no mistake. This move to a double-digit major version number is going to cause serious pain. We will do our best to fix, hack, slash, and whatever around it, but right now the focus is the last of our remaining single-digit releases. Until that is out the door, do not be expecting tree-wide commits to fix things. -aDe