This is the result of emerge -upv world today: [blocks B ] <kde-base/kdelibs-3.1.4 (from pkg x11-libs/qt-3.2.1) [ebuild U ] x11-libs/qt-3.2.1 [3.1.2-r4] +cups +nas +postgres +opengl +mysql Peter Hilbring
qt.3.2.1 has the following depend: !<kde-base/kdelibs-3.1.4 and in kdelibs-3.1.4 it says: qtver-from-kdever ${PV} need-qt $selected_version I think thats the problem. A circ. dep as usual.
the KDE guys can correct me but there is no bug here versions *less than* 3.1.4 are blocked by the new QT ... so `emerge -C kdelibs` and then update
Yeah, I think this is what we want. The main problem is that if you upgrade Qt to 3.2.1, you then need to upgrade kde to at least 3.1.4. I think forcing this block is probably the best thing to do here.
------- Additional Comments From howard_b_golden@yahoo.com 2003-18-09 11:40 EST ------- In the qt-3.2.1.ebuild, the line: !<kde-base/kdelibs-3.1.4 should do what you want, but it DOESN'T! Perhaps this is a problem with Portage. I changed the line to: >=kde-base/kdelibs-3.1.4 and the block was gone (after upgrading to kde-3.1.4). So, my point is, either fix the ebuild (change "!<" to ">=") or fix Portage. I don't think this is resolved!
umm we really cant have qt depend on kdelibs and vice versa ... the DEPEND does work to a degree ... you unmerge the older kdelibs which wont work, emerge qt and update KDE and you're done
*** Bug 29351 has been marked as a duplicate of this bug. ***
Shouldn't kdelibs 2 be excluded from the block dependency ? it use qt 2 instead of qt 3 so there shouldn't be any problem and if we remove kdelibs 2 some apps won't work
*** Bug 33299 has been marked as a duplicate of this bug. ***
I'm also curious if the block could be restricted to kdelibs-3. I guess if "emerge -epo world | grep kdelibs" does not list kdelibs-2, it is likely that most of my apps will still work after unmerging kdelibs-2. Is that right? (I will post here if I experience otherwise...)
yes, your apps would work fine after unmerging kdelibs2 (unless you have apps that only work with kdelibs2)
*** Bug 34493 has been marked as a duplicate of this bug. ***