Date: Tue, 27 Sep 2011 06:35:42 +0000 From: h h <aakuusta@gmail.com> To: Kevin Oberman <kob6558@gmail.com> Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org, ade@freebsd.org Subject: Re: HEADS UP: ports/ and 10.0-CURRENT Message-ID: <86mxdqfq69.fsf@gmail.com> In-Reply-To: <CAN6yY1t5wJ3%2B4LG=upL6sR7tSNU6Uhx-y=L0AJm6rKFsKnvPiQ@mail.gmail.com> (Kevin Oberman's message of "Mon, 26 Sep 2011 21:56:26 -0700") References: <20110926230335.041fd9aa@lab.lovett.com> <CAN6yY1t5wJ3%2B4LG=upL6sR7tSNU6Uhx-y=L0AJm6rKFsKnvPiQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman <kob6558@gmail.com> writes: > On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett <ade@freebsd.org> 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'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86mxdqfq69.fsf>