Leo Famulari <l...@famulari.name> skribis: > On Wed, Nov 09, 2016 at 09:40:05PM +0100, Ludovic Courtès wrote:
[...] >> The long-term goal is to rebuild everything with a compiler that has >> this patch, in the next ‘core-updates’. We might as well switch to GCC >> 5 as the default compiler. >> >> In the meantime, the only approach I can think of is to (1) ungraft more >> frequently than we’ve done so far, and (2) when we ungraft a package, >> add gcc@5 as an input such that it gets rebuilt without the problem. >> >> Thoughts? > > Sounds good to me. I wonder, with our current build farm, how often can > we do the full rebuilds required by ungrafting? I don't yet have a sense > of how long it takes. I don’t know exactly. I have a feeling that the build farm has been underused over the last couple of weeks for instance, but no precise stats. I’d like to be able to gather usage stats so we can see when the right time for rebuilds comes. For now I think we’ll merge core-updates Real Soon, and then start a staging branch or the python-updates one. Ludo’.
