# ls -1 ChangeLog Manifest metadata.xml perl-Math-BigRat-0.260.300.ebuild perl-Math-BigRat-0.260.400.ebuild perl-Math-BigRat-0.260.600.ebuild # ls -1 ChangeLog Manifest Math-BigRat-0.260.200-r1.ebuild metadata.xml I'm assuming anyone responsible for this has perl 5.20 installed as that also satisfies the virtual's dep. (The current situation is that you cannot install Math-BigInt as it depends on virtual/perl-Math-BigRat which refuses to install since the corresponding version does not exist.) I believe the correct solution is to bump the perl-core/Math-BigRat ebuild to the latest release which is 0.260.600.
On second thought, it appears that the virtual for 0.260.600 is masked, so the correct solution is probably to add back the virtual for 0.260.200.
huettel@pinacolada ~/Gentoo/gentoo-x86/virtual/perl-Math-BigRat $ grep =dev-lang/perl- * grep: CVS: Ist ein Verzeichnis perl-Math-BigRat-0.260.300.ebuild: || ( =dev-lang/perl-5.16* ~perl-core/${PN#perl-}-${PV} ) perl-Math-BigRat-0.260.400.ebuild: || ( =dev-lang/perl-5.18* ~perl-core/${PN#perl-}-${PV} ) perl-Math-BigRat-0.260.600.ebuild: || ( =dev-lang/perl-5.20* ~perl-core/${PN#perl-}-${PV} ) huettel@pinacolada ~/Gentoo/gentoo-x86/virtual/perl-Math-BigRat $ eshowkw perl-Math-BigRat Keywords for virtual/perl-Math-BigRat: | | u | | a a a p s | n | | l m r h i m m p s p | u s | r | p d a m p a 6 i p c 3 a x | s l | e | h 6 r 6 p 6 8 p p 6 9 s r 8 | e o | p | a 4 m 4 a 4 k s c 4 0 h c 6 | d t | o -------------+-----------------------------+-----+------- 0.260.300 | + + + o + + o ~ + o + + + + | o 0 | gentoo [I]0.260.400 | + ~ ~ o ~ ~ o ~ ~ o ~ ~ ~ ~ | o | gentoo [M]0.260.600 | ~ ~ ~ o ~ ~ o ~ ~ o ~ ~ ~ ~ | o | gentoo huettel@pinacolada ~/Gentoo/gentoo-x86/virtual/perl-Math-BigRat $ I.e., use .300 with Perl 5.16 (stable), .400 with Perl 5.18 (testing, to be stabilized), .600 with Perl 5.20 (masked). All three versions are valid for BigInt.
Can you explain to me how you use .300 and .400 when there are no ebuilds for them in the tree?
Ohhh... Oops, I guess earlier when testing, because BigInt wasn't updated yet it conflicted in a way that portage couldn't resolve, but uninstalling and reinstalling some stuff and it all seems to resolve itself now, sorry for the noise then :).