Is there any particular reason dev-tex/biber-1.7 has been dropped? I do not want to upgrade to 1.8 because it indirectly depends on perl-5.18 (via dev-perl/autovivification) and perl-5.18 is not stable yet. I am running an almost stable system and do not want to maintain long keyword lists. So it would be nice if biber-1.7 would still be supported in main tree until perl-5.18 is becoming stable. Also having a stable biber version in the future whould be nice, but I will file a separate bug report on this. Reproducible: Always
It isn't gone. You can put the ebuild in a local overlay if you want.
(In reply to Jeroen Roovers from comment #1) > It isn't gone. You can put the ebuild in a local overlay if you want. Thats what I did. But maybe I am not the only one with this concern and it would be nice to know if biber-1.7 is still supported in some way or maybe has been removed because of serious known issues.
Can you paste your dependency tree? You should not need to install perl 5.18 for biber-1.8. It works with perl 5.16.2
I just saw Portage was wrong about blaming dev-perl/autovivification for depending on perl-5.18. Really it is virtual/perl-Exporter-5.680.0 which depends on >=dev-lang/perl-5.17.11
Ok, I found out I can use perl-core/Exporter-5.680.0 as provider for virtual/perl-Exporter-5.680.0 by kewording it. Then I am able to use it with perl-5.16. Sorry for the noise and thanks for your help!