From owner-freebsd-ports@FreeBSD.ORG Thu Mar 10 20:53:08 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7229B1065676; Thu, 10 Mar 2011 20:53:08 +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 4C16E8FC17; Thu, 10 Mar 2011 20:53:08 +0000 (UTC) Received: from cpe-66-68-128-204.austin.res.rr.com ([66.68.128.204] helo=[172.16.32.150]) by panix.lovett.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1Pxmr5-0006lG-Id; Thu, 10 Mar 2011 20:53:07 +0000 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Ade Lovett In-Reply-To: <4D7932AC.1020508@FreeBSD.org> Date: Thu, 10 Mar 2011 14:52:56 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <883EDE8E-309A-497B-A9ED-2350AC1D2546@FreeBSD.org> References: <488C7790-D3E2-4441-BEC8-DD26D8917181@freebsd.org> <4D792578.6000303@FreeBSD.org> <2B21F26B-D7EA-480B-BFA2-BD12DDDB7721@FreeBSD.org> <4D7932AC.1020508@FreeBSD.org> To: FreeBSD Ports X-Mailer: Apple Mail (2.1082) Cc: Doug Barton Subject: Re: [HEADS UP] GNU make 3.82 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: Thu, 10 Mar 2011 20:53:08 -0000 On Mar 10, 2011, at 14:21 , Doug Barton wrote: > What I'm suggesting is that the URL for the logs of that run get = posted here, along with contacting the maintainers of the affected = ports. Then let's see what people have to say about getting them fixed = sooner rather than later. Can you explain why doing that would be a bad = idea? Those 50 or so ports are not the complete picture. Some of them are = preventing other ports from being built. So, we cycle through an -exp = run adding USE_GMAKE=3D381 (it's not a library or anything, just an = executable, and in the context of clean building, only one or the other = will exist for a specific port -exp build, so there's no question of = interaction) until we have _all_ of the affected ports. Then the list gets posted somewhere, USE_GMAKE=3D381 goes active, then = there's a period (6-7 months) for folks to clean things up, at which = point USE_GMAKE=3D381 does exactly the same as USE_GMAKE=3Dyes (use = gmake-3.82) -- ports that get fixed after this date simply change = USE_GMAKE=3D381 -> USE_GMAKE=3Dyes (cosmetic change only), and a list of = known-broken ports can still be determined by grepping for = 'USE_GMAKE=3D381'. If updates to those ports fix them, change USE_GMAKE = back to 'yes'. > I admire your optimism, however experience tells us that once these = types of accomodations get into the tree, they stay there for a long = time. There is no issue of optimism about it. gmake-3.82 _will_ be the sole = version of GNU make in the tree by (at latest) the end of this year. -aDe