Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Sep 2011 21:04:44 +0200
From:      Vlad Galu <dudu@dudu.ro>
To:        Gleb Kurtsou <gleb.kurtsou@gmail.com>
Cc:        ports@FreeBSD.org, current@FreeBSD.org, Ade Lovett <ade@FreeBSD.org>
Subject:   Re: HEADS UP: ports/ and 10.0-CURRENT
Message-ID:  <CF7BA9CE-C3A1-49CE-AE94-9EDF2B383C22@dudu.ro>
In-Reply-To: <20110927185043.GA84488@tops>
References:  <20110926230335.041fd9aa@lab.lovett.com> <20110927185043.GA84488@tops>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 27, 2011, at 8:50 PM, Gleb Kurtsou wrote:
> On (26/09/2011 23:03), 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.
>>=20
>> 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".
>=20
> It's more exciting than that. FreeBSD >=3D 10 is already seized by
> Apple :)
>=20
> =
http://www.google.com/codesearch#search/&q=3D__FreeBSD__%5CW%2B10&type=3Dc=
s
>=20

That seems to be a FUSE-ism. __FreeBSD__  isn't defined anywhere on my =
OSX system.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF7BA9CE-C3A1-49CE-AE94-9EDF2B383C22>