From owner-freebsd-current@FreeBSD.ORG  Tue Sep 27 04:29:37 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 484C9106566C
	for <current@FreeBSD.org>; Tue, 27 Sep 2011 04:29:37 +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 2290B8FC17
	for <current@FreeBSD.org>; Tue, 27 Sep 2011 04:29:36 +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 <ade@FreeBSD.org>)
	id 1R8OtX-000B00-CH; Tue, 27 Sep 2011 04:03:47 +0000
Date: Mon, 26 Sep 2011 23:03:35 -0500
From: Ade Lovett <ade@FreeBSD.org>
To: ports@FreeBSD.org, current@FreeBSD.org
Message-ID: <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: HEADS UP: ports/ and 10.0-CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ade@FreeBSD.org
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2011 04:29:37 -0000

With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be
expected, ports/ is going to be essentially unusable for a while.

The issue stems from configure scripts (to choose something completely
at random) assuming that FreeBSD would never jump to a double-digit
major version number, and as such, various regexps for "freebsd1*" (ie:
FreeBSD 1.1.x) are now matching "freebsd10".

This is going to be some fairly fundamental breakage.

However, until such time as 9.0-RELEASE is completely out of the door,
with autotools hat on, I will _not_ be committing any changes to
infrastructural ports to "fix" this.

That is to say, until 9.0-R happens, and for some considerable period
afterwards, ya'll can pretty much expect ports/ to be non-functional on
HEAD.  PRs mentioning this will be gleefully closed referencing this
message.

-aDe

Reply-To set to me.  Please honor it.