A month have passed without issues and this will let other stable packages to also rely on this sooner
err, no, this can't be stabilized anytime soon :)
llvm-3.7.0 (which we want to stabilize) depends on binutils-libs. It's been another month -- can we stabilize now? I'm guessing no, since the bugs you linked are still open.
(In reply to Matt Turner from comment #2)
> llvm-3.7.0 (which we want to stabilize) depends on binutils-libs. It's been
> another month -- can we stabilize now? I'm guessing no, since the bugs you
> linked are still open.
Maybe now? The radeon driver has dropped support for LLVM 3.5 and the branch for the next Mesa release is being made this Friday.
Author: Marek Olšák <email@example.com>
Date: Wed Feb 10 21:48:59 2016 +0100
gallium/radeon: drop support for LLVM 3.5
Moreover, being a few releases behind LLVM is bad because the people developing the drivers using it aren't using (or often testing) old releases of LLVM -- but we're still not offering anything newer in stable.
Can we please stabilize this, so that llvm-3.7 can be stabilized, so I can avoid a disaster when it's time to stabilize the next version of Mesa?
i think we have a handle now on the failures w/newer binutils, and it should be restricted to just a few packages. so we can stabilize these versions now.
Calculating dependencies... done!
[ebuild U ~] sys-devel/binutils-config-5-r2::gentoo [4-r2::gentoo] 0 KiB
[ebuild N ~] sys-libs/binutils-libs-2.25.1-r2:0/2.25.1::gentoo USE="multitarget nls zlib -64-bit-bfd -static-libs" 0 KiB
[blocks B ] <app-admin/eselect-1.4.5 ("<app-admin/eselect-1.4.5" is blocking sys-devel/binutils-config-5-r2)
(In reply to Jeroen Roovers from comment #5)
moved eselect request to bug 574974
i've done the rest now