From owner-freebsd-current@FreeBSD.ORG Tue Sep 27 08:28:50 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99D6A106566B; Tue, 27 Sep 2011 08:28:50 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 536B28FC0C; Tue, 27 Sep 2011 08:28:50 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1R8T21-0002vh-Ck>; Tue, 27 Sep 2011 10:28:49 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1R8T21-0001V0-Ae>; Tue, 27 Sep 2011 10:28:49 +0200 Message-ID: <4E818941.7060006@zedat.fu-berlin.de> Date: Tue, 27 Sep 2011 10:28:49 +0200 From: "O. Hartmann" Organization: Freie =?ISO-8859-1?Q?Universit=E4t_Berlin?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.2) Gecko/20110907 Thunderbird/6.0.2 MIME-Version: 1.0 To: h h References: <20110926230335.041fd9aa@lab.lovett.com> <86mxdqfq69.fsf@gmail.com> In-Reply-To: <86mxdqfq69.fsf@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: ade@freebsd.org, freebsd-current@freebsd.org, freebsd-ports@freebsd.org 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 08:28:50 -0000 On 09/27/11 08:35, h h wrote: > Kevin Oberman writes: > >> On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote: >> >>> 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". > [...] >> >> aDe, >> >> Could an entry to this effect be added to UPDATING (with a matching >> entry when ports/ is "unbroken"). > > Also mention a workaround, e.g. > > $ export UNAME_r='9.9-BLAH' Now I understand why some OS vendors have choosen the latin 10 'X' for their tenth version of their operating system ...