Alan E. Davis wrote: > > I have read a number of different explanations and suggestions, some > of them regarding an earlier, yet similar, tanglement between versions > of qt-*. I've tried a number of suggestions, and I have unmerged and > remerged packages. > > I am now trying to individually merge packages with dependencies on > qt-*-4.5.2. > > I tried KDE 4.3.1, with some trepidation, and I have happily been > running gnome, save a couple of nits, and I have run into qt issues in > the past. I would like to uninstall kde4 (like it, but not well > enough to devote so many resources to it, and to have to upgrade > frequently and painfully). I would like to remove the KDE 4 > installation, but keep the individual packages depending on kdelibs. > (K3b, etc.). Would this have an impact on this issue? This is off > topic, but how to uninstall EXCEPT what I want, of KDE4? Is this > reasonable? > > Thanks. I hope to solve this soon, but it's too early to know > whether the help on this list was enough. I changed USE flags, and > the same messages appear: > > <<SNIP >> > > Thank you, > > Alan >
Does this help any? r...@smoker / # eselect news read 6 2009-09-27-qt_use_changes Title Qt 4.5.2 default USE flag changes Author Alex Alexander <wi...@gentoo.org> Posted 2009-09-27 Revision 1 Qt version 4.5.2 has significant changes in the USE flags enabled by default. When upgrading, make sure you check and re-enable any USE flags you need. Depending on your system and installed packages, you might hit an issue where Portage is getting confused by this USE flag change, trying to mix old 4.5.1 ebuilds with new 4.5.2 ones, resulting in blocks. If this happens to you, please add the offending USE flags (usually 'qt3support' and 'dbus') in your USE= or switch to a desktop profile (eselect profile list). Check this post [0] for more details on this issue. [0] http://www.linuxized.com/p192 r...@smoker / # I have this in my USE flags and I didn't run into this that I recall. qt3 qt3support qt4 I think they are planning to remove qt3 in the future. I'm not sure how close that future is tho. I think qt3support is the key here. Dale :-) :-)
