On Sunday 28 June 2009 16:12:26 walt wrote:
> On 06/27/2009 07:24 PM, Andrew Gaydenko wrote:
> > On Sunday 28 June 2009 02:54:59 walt wrote:
> >> On 06/27/2009 03:32 PM, Andrew Gaydenko wrote:
> >>> make.conf hasn't qt3support at all. Adding qt3support to qt-opengl
> >>> shows... well... something horrible (see below) :-)
> >>>
> >>> //=====================================================================
> >>>= emerge -pvDuN world
> >>>
> >>> These are the packages that would be merged, in order:
> >>>
> >>> Calculating dependencies... done!
> >>> [ebuild U ] x11-libs/qt-core-4.5.2 [4.5.1] USE="glib iconv
> >>> qt3support ssl -debug -doc -pch" 0 kB [ebuild U ]
> >>> x11-libs/qt-test-4.5.2 [4.5.1] USE="iconv -debug -pch" 0 kB [blocks b
> >>> ]<x11-libs/qt-test-4.5.2 ("<x11-libs/qt-test-4.5.2" is blocking
> >>> x11-libs/qt-assistant-4.5.2, x11-
> >>
> >> I recently went through the same thing on ~amd64 and emerge made me
> >> uninstall every qt package before it would start building the updates.
> >> I have no idea why, but everything finally came out okay.
> >>
> >> I'd say go ahead and emerge -C all of those qt blockers as emerge
> >> suggests.
> >
> > Walt, thanks! At my case portage has ovecome those blocks without direct
> > unmerging.
>
> Ah, I see portage wants to update my qt4 *again* today, and I see a new
> package comment that emerging "qt" will pull in more qt sub-packages than
> I probably want -- very true. So now I'm just emerging qt-core instead.
> I hope it has everything that VirtualBox needs. I'll see.
You do not need qt-anything in world. It is a library, and ebuilds pull it in
as needed.
Remove all mention of qt ebuilds from the world file and double check that
things are still correct via a null output from
emerge -uND world
emerge --depclean
Then add USE="qt3support" to make.conf
--
alan dot mckinnon at gmail dot com
