svn commit: r332557 - head/lang/gcc

[Tijl Coosemans]

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.