Joshua Kinard wrote: > Using seed stage3 stages I built 6 months ago (but never released due > to getting sidetracked), I run into errors like this: > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > dev-lang/perl:0 > > (dev-lang/perl-5.20.1-r4:0/5.20::gentoo, ebuild scheduled for merge) pulled > in by > =dev-lang/perl-5.20* required by > (virtual/perl-ExtUtils-ParseXS-3.240.0:0/0::gentoo, ebuild scheduled for > merge) > ^ ^^^^^ > (and 16 more with the same problem) > > (dev-lang/perl-5.18.2-r2:0/5.18::gentoo, ebuild scheduled for merge) pulled > in by > dev-lang/perl:0/5.18=[-build(-)] required by > (dev-perl/libintl-perl-1.230.0:0/0::gentoo, installed) > ^^^^^^^^ > =dev-lang/perl-5.18* required by > (virtual/perl-ExtUtils-Manifest-1.630.0-r1:0/0::gentoo, installed) > ^ ^^^^^ > (and 2 more with the same problems) > > It's hard to read mess like that and trace down the offending package, > fix it, and make catalyst happy.
Lots of dev-perl packages have specific minor version dependencies on dev-lang/perl, maybe because sometimes the package is included in perl and sometimes not. It's a f*ing mess. You have to look up all your installed dev-perl packages manually and find which ones are either too old to know about perl-5.20 or not compatible with it, and then you have to unmerge those manually. > Kinda defeats the purpose of catalyst in the first place. The proper way is to build stage1+2+3 yourself, then this mess doesn't happen. But like you I too cheat a little, and have to deal with the mess. //Peter
