From owner-freebsd-ports@FreeBSD.ORG Sat Mar 12 05:14:51 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 0201F106566C for ; Sat, 12 Mar 2011 05:14:51 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from doug-optiplex.ka9q.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 9405415102D for ; Sat, 12 Mar 2011 05:14:50 +0000 (UTC) Message-ID: <4D7B014A.7050503@FreeBSD.org> Date: Fri, 11 Mar 2011 21:14:50 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110304 Thunderbird/3.1.9 MIME-Version: 1.0 To: FreeBSD Ports References: <488C7790-D3E2-4441-BEC8-DD26D8917181@freebsd.org> <4D792578.6000303@FreeBSD.org> <2B21F26B-D7EA-480B-BFA2-BD12DDDB7721@FreeBSD.org> <4D7932AC.1020508@FreeBSD.org> <883EDE8E-309A-497B-A9ED-2350AC1D2546@FreeBSD.org> <20110310235432.GA11144@lonesome.com> <4D796857.1020305@FreeBSD.org> <1150BA48-1B1D-4C8E-9059-ADF5CE2C494C@FreeBSD.org> <20110311050510.GA16469@lonesome.com> In-Reply-To: <20110311050510.GA16469@lonesome.com> X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Sat, 12 Mar 2011 05:14:51 -0000 On 03/10/2011 21:05, Mark Linimon wrote: > I answered this question last night on IRC, aDe answered it in email: > >> What is the urgency in upgrading gmake that prevents "fix the broken >> ports first" as an option to at least explore? > > Now that gmake is out, if the past is any indication, some project > will quickly upgrade to it. We can wait for that to happen, and then > have to scramble, or we can get ahead of the curve. I can see why that would make it an important problem, but I don't see why that makes the problem so urgent that sharing it with the community and asking them for suggestions can't be done first; especially considering that there is at least one workable plan in the wings if no one comes up with something better. > Not every single change to the Ports Collection rises to the level of > requiring a committee meeting to generate a consensus. IMHO this does > not. It's really, really frustrating to me when I spend time trying to make myself clear and you consistently mischaracterize it. I can't tell if you're doing it on purpose, I'm failing to communicate, or something else is going on. But just to be clear, I'm not talking about making a committee decision. I'm talking about making the information about the problem available to the community. > In this case it was "here is someone willing to do the work, here's > an action plan, let's just do it." And while that sounds noble and all, it's the wrong road to go down. There are way too many things happening "in private" around here and the only way to solve that problem is to open the doors. Meanwhile, while I appreciate you answering one of my questions, but you still haven't answered arguably the more important one. What harm will come from publicizing this problem and asking for help from the community? On 03/10/2011 21:25, Ade Lovett wrote: > How about working from the basis that perhaps, just perhaps, I'm > _right_, and show me why _I_ am wrong. I can't help thinking that the fact that when I say, "Let's ask the community for input on this topic" you _hear_ me saying, "You're wrong" is part of the problem. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/