From owner-freebsd-ports@FreeBSD.ORG Tue Sep 27 04:56:27 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B18B1065674; Tue, 27 Sep 2011 04:56:27 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0010A8FC15; Tue, 27 Sep 2011 04:56:26 +0000 (UTC) Received: by iadk27 with SMTP id k27so8418108iad.13 for ; Mon, 26 Sep 2011 21:56:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=JzFLyotpJ1RXCYbiiDZ1GTVGpwKXDvV7C9u98y1dVDI=; b=cnM11WM173sBjIdRVgqlTKwq1kwMhiXbCKaQvJKFOgLFZtAYM0CAlnY4xE1zje752T HvyUa3T64ivjqMFW06p4aw54jJJnCODEHSZz6Rkxm2YQHw19Nb1owS59L9mb+th5csem Tu1wYioknflmruoEG0t6B7mNXMUbO6K/BBFGE= MIME-Version: 1.0 Received: by 10.231.82.131 with SMTP id b3mr9456547ibl.74.1317099386293; Mon, 26 Sep 2011 21:56:26 -0700 (PDT) Received: by 10.231.36.69 with HTTP; Mon, 26 Sep 2011 21:56:26 -0700 (PDT) In-Reply-To: <20110926230335.041fd9aa@lab.lovett.com> References: <20110926230335.041fd9aa@lab.lovett.com> Date: Mon, 26 Sep 2011 21:56:26 -0700 Message-ID: From: Kevin Oberman To: ade@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org, current@freebsd.org Subject: Re: HEADS UP: ports/ and 10.0-CURRENT X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Sep 2011 04:56:27 -0000 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". > > 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. =A0PRs mentioning this will be gleefully closed referencing this > message. aDe, Could an entry to this effect be added to UPDATING (with a matching entry when ports/ is "unbroken"). Anyone running CURRENT should be reading your message, but I'm a "belt and suspenders" type of guy on this sort of thing. Backing out of CURRENT and moving to 9-STABLE can be a REAL pain that will likely rapidly get worse as HEAD gets less and less frozen. --=20 R. Kevin Oberman, Network Engineer - Retired E-mail: kob6558@gmail.com