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