From owner-svn-ports-all@FreeBSD.ORG  Mon Dec  9 15:15:14 2013
Return-Path: <owner-svn-ports-all@FreeBSD.ORG>
Delivered-To: svn-ports-all@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0BA7A519;
 Mon,  9 Dec 2013 15:15:14 +0000 (UTC)
Received: from mailrelay005.isp.belgacom.be (mailrelay005.isp.belgacom.be
 [195.238.6.171])
 by mx1.freebsd.org (Postfix) with ESMTP id DC6931238;
 Mon,  9 Dec 2013 15:15:12 +0000 (UTC)
X-Belgacom-Dynamic: yes
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtwIAETdpVJbsKXL/2dsb2JhbABZgwe2IXmDBoEuF3SCJQEBBTocIxALGAklDyoeBogZAcE7F48QB4QzA5gTkhSDKjs
Received: from 203.165-176-91.adsl-dyn.isp.belgacom.be (HELO
 kalimero.tijl.coosemans.org) ([91.176.165.203])
 by relay.skynet.be with ESMTP; 09 Dec 2013 16:15:11 +0100
Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org
 [127.0.0.1])
 by kalimero.tijl.coosemans.org (8.14.7/8.14.7) with ESMTP id rB9FF9CD003248;
 Mon, 9 Dec 2013 16:15:10 +0100 (CET) (envelope-from tijl@FreeBSD.org)
Date: Mon, 9 Dec 2013 16:15:09 +0100
From: Tijl Coosemans <tijl@FreeBSD.org>
To: Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: svn commit: r332557 - head/lang/gcc
Message-ID: <20131209161509.55b7a820@kalimero.tijl.coosemans.org>
In-Reply-To: <alpine.LNX.2.00.1312082252220.2197@tuna.site>
References: <201311022320.rA2NKEcg089316@svn.freebsd.org>
 <20131103110034.GA80884@graf.pompo.net>
 <alpine.LNX.2.00.1311031456490.3029@tuna.site>
 <52765ED2.8080205@marino.st>
 <alpine.LNX.2.00.1312082252220.2197@tuna.site>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: svn-ports-head@freebsd.org, Thierry Thomas <thierry@FreeBSD.org>,
 svn-ports-all@freebsd.org, John Marino <marino@freebsd.org>,
 ports-committers@freebsd.org
X-BeenThere: svn-ports-all@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SVN commit messages for the ports tree <svn-ports-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-ports-all/>
List-Post: <mailto:svn-ports-all@freebsd.org>
List-Help: <mailto:svn-ports-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-ports-all>,
 <mailto:svn-ports-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Dec 2013 15:15:14 -0000

On Sun, 8 Dec 2013 22:55:47 +0100 (CET) Gerald Pfeifer wrote:
> On Sun, 3 Nov 2013, John Marino wrote:
>> However, food for thought: Moving to gcc47 and exposing the resulting
>> package could have the benefit of others providing the fixes.  I can
>> tess you from experience these last 3 weeks that c++ breakage is very
>> slow to fix so people will be waiting a long time.
> 
> Luckily I had a great volunteer who has been helping with regular 
> packages, and the python crew has been responsive on the python issue 
> this upgrade ran into, but you have a very good point:  Putting everyone
> who wants to improve general infrastructure on the hook to fix all 
> broken (and not broken because the update is bad, but because the
> port has issues) ports, is tough and discourages such changes.
> 
> That's why the libmpc update has taken so long and now the lang/gcc
> update to GCC 4.7 is taking so long (though that one appears to be
> a matter of only four more weeks if we are lucky).

I don't think anyone would complain if you did something like this:

Do exp-run.  If successful, commit; otherwise contact maintainers and
ask for patches.  Once you've collected a number of fixes do another
exp-run.  Repeat until you get a successful run.  If maintainers don't
respond in say 2 weeks mark their ports broken in your patch.