How about that?
Not sure about it, building the library is quite stable, but there are some unfixed bugs in this release that may make it worth waiting for vc-1.3.4: https://github.com/VcDevel/Vc/issues/177 https://github.com/VcDevel/Vc/issues/191 https://github.com/VcDevel/Vc/issues/194 https://github.com/VcDevel/Vc/issues/200
Vc 1.4.0 has been released a couple of weeks ago: https://github.com/VcDevel/Vc/releases/tag/1.4.0 Unfortunately, the new version brings in some API breakage and doesn't build with FEATURES=test. I will put the update on hold until these issues are fixed in subsequent releases upstream, and see if I can backport fixes to the issues above to be able to proceed with stabilization of 1.3.3 instead.
Vc-1.4.1 has fixes for the issues linked above. I think I will go ahead and stabilize that version instead of 1.3.3. What do you think?
You are the boss. ;)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0a6edf54c6732cb2b19ece30fd9ebde8f159a06e commit 0a6edf54c6732cb2b19ece30fd9ebde8f159a06e Author: Guilherme Amadio <amadio@gentoo.org> AuthorDate: 2019-05-08 08:43:14 +0000 Commit: Guilherme Amadio <amadio@gentoo.org> CommitDate: 2019-05-08 08:44:07 +0000 dev-libs/vc: stabilize 1.4.1 for amd64 and x86 Closes: https://bugs.gentoo.org/658138 Package-Manager: Portage-2.3.66, Repoman-2.3.12 Signed-off-by: Guilherme Amadio <amadio@gentoo.org> dev-libs/vc/vc-1.4.1.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
