1 |
On 02/12/2015 08:15 AM, Gevisz wrote: |
2 |
> # emerge --ask chromium |
3 |
> ... |
4 |
>> The following USE changes are necessary to proceed: |
5 |
>> (see "package.use" in the portage(5) man page for more details) |
6 |
>> # required by www-client/chromium-40.0.2214.111 |
7 |
>> # required by chromium (argument) |
8 |
>>> =dev-libs/libxml2-2.9.2 icu |
9 |
> Ok, done. |
10 |
> |
11 |
> # emerge --ask chromium |
12 |
> ... |
13 |
>> !!! Multiple package instances within a single package slot have been pulled |
14 |
>> !!! into the dependency graph, resulting in a slot conflict: |
15 |
>> |
16 |
>> dev-libs/libxml2:2 |
17 |
>> |
18 |
>> (dev-libs/libxml2-2.9.2:2/2::gentoo, ebuild scheduled for merge) pulled in by |
19 |
>> dev-libs/libxml2:=[icu] required by (www-client/chromium-40.0.2214.111:0/0::gentoo, ebuild scheduled for merge) |
20 |
>> ^^^ > |
21 |
>> |
22 |
>> (dev-libs/libxml2-2.9.2:2/2::gentoo, installed) pulled in by |
23 |
>> dev-libs/libxml2:2[!icu?] required by (dev-qt/qtwebkit-4.8.5:4/4::gentoo, installed) |
24 |
>> ^^^^^ > |
25 |
>> It may be possible to solve this problem by using package.mask to |
26 |
>> prevent one of those packages from being selected. However, it is also |
27 |
>> possible that conflicting dependencies exist such that they are |
28 |
>> impossible to satisfy simultaneously. If such a conflict exists in |
29 |
>> the dependencies of two different packages, then those packages can |
30 |
>> not be installed simultaneously. You may want to try a larger value of |
31 |
>> the --backtrack option, such as --backtrack=30, in order to see if |
32 |
>> that will solve this conflict automatically. |
33 |
|
34 |
I think (emphasis on the think) that qtwebkit needs libxml2 with -icu, |
35 |
and chromium needs libxml2 with +icu. As far as I can tell from reading |
36 |
a couple bug reports, it looks like you can rebuild qtwebkit with |
37 |
-gstreamer (since that's what causes the !icu? blocker) and then you |
38 |
should be able to install chromium. Apparently icu is pretty annoying. |
39 |
|
40 |
Alternatively, you could just uninstall qtwebkit if you're not using it |
41 |
for anything. |
42 |
|
43 |
Alec |