1 |
On 06/27/2009 07:24 PM, Andrew Gaydenko wrote: |
2 |
> On Sunday 28 June 2009 02:54:59 walt wrote: |
3 |
>> On 06/27/2009 03:32 PM, Andrew Gaydenko wrote: |
4 |
>>> make.conf hasn't qt3support at all. Adding qt3support to qt-opengl |
5 |
>>> shows... well... something horrible (see below) :-) |
6 |
>>> |
7 |
>>> //====================================================================== |
8 |
>>> emerge -pvDuN world |
9 |
>>> |
10 |
>>> These are the packages that would be merged, in order: |
11 |
>>> |
12 |
>>> Calculating dependencies... done! |
13 |
>>> [ebuild U ] x11-libs/qt-core-4.5.2 [4.5.1] USE="glib iconv qt3support |
14 |
>>> ssl -debug -doc -pch" 0 kB [ebuild U ] x11-libs/qt-test-4.5.2 [4.5.1] |
15 |
>>> USE="iconv -debug -pch" 0 kB [blocks b ]<x11-libs/qt-test-4.5.2 |
16 |
>>> ("<x11-libs/qt-test-4.5.2" is blocking x11-libs/qt-assistant-4.5.2, x11- |
17 |
>> |
18 |
>> I recently went through the same thing on ~amd64 and emerge made me |
19 |
>> uninstall every qt package before it would start building the updates. I |
20 |
>> have no idea why, but everything finally came out okay. |
21 |
>> |
22 |
>> I'd say go ahead and emerge -C all of those qt blockers as emerge suggests. |
23 |
> |
24 |
> Walt, thanks! At my case portage has ovecome those blocks without direct |
25 |
> unmerging. |
26 |
|
27 |
Ah, I see portage wants to update my qt4 *again* today, and I see a new |
28 |
package comment that emerging "qt" will pull in more qt sub-packages than |
29 |
I probably want -- very true. So now I'm just emerging qt-core instead. |
30 |
I hope it has everything that VirtualBox needs. I'll see. |