Hartmut Goebel <h.goe...@crazy-compilers.com> skribis:
> Am 13.10.2016 um 22:12 schrieb Ludovic Courtès:
>> It’s a good idea, but it would entail a rebuild of 1,000+ packages. Can
>> you save it for the next big-rebuild cycle?
> No problem.
> Still have to learn what "next big-rebuild cycle" means. Is there a
> branch for it?
Well there’s core-updates for changes that trigger a rebuild of 90% of
the packages, and then occasionally topic branches (‘python-updates’,
Once ‘core-updates’ is merged (hopefully in a few days), we could start
a ‘staging’ branch and put changes that require between ~300 and ~1200
rebuilds. The idea would be to close the branch much more quickly than
core-updates (the changes should be less disruptive, with little chance
of breaking things.)