Hi All, Qt 4.2 needs dbus 0.62 and dbus has qt as a dependency. To get Qt emerging I've just emerged dbus with nodeps (seeing an earlier qt is already installed). Not sure how you need to handle this - let me know if you need any further info from me. Cheers, Alan.
actually the nodeps thing didn't work...
that's even worse with cups, which needs dbus. and qt needs cups. try USE="dbus cups qt3 qt4" emerge cups. qt3/4 won't build due to missing cups headers and so on :/ i think portage should at least try to detect circular deps (and give a warning/suggestion). cups builds quickly, so it's no big deal, but if i would have to rebuild both qt packages....
QT 4.2 is a beta pre-release and should NOT be compiled against dbus versions under 0.90. That dbus version was released on 7/17, however all the necessary bindings have not been released yet. QT 4.2 contains the bindings for dbus 0.90, however versions of QT below this actually had to be installed for dbus itself to build the bindings. Basically QT 4.2 beta pre-release (read.. this is still considered PRE beta by TrollTech) is masked and keyworded -*, if you unmask and keyword a package... and it breaks... you get to keep the pieces.
ahhhh ok - my bad - sorry. I assumed bugs should be logged on masked packages as well.
Basically QT 4.2 beta pre-release (read.. this is still considered PRE beta by TrollTech) is masked and keyworded -*, if you unmask and keyword a package... and it breaks... you get to keep the pieces. Says it all.
(In reply to comment #5) > Basically QT 4.2 beta pre-release (read.. this is still considered PRE beta by > TrollTech) is masked and keyworded -*, if you unmask and keyword a package... > and it breaks... you get to keep the pieces. qt-4.2.1 is now unmasked and keyworded ~arch, so qt emerges OK but is caught in a upgrade/downgrade loop as dbus-0.62-r1 has RDEPEND =qt-4.1*.
And it's remasked. No idea what caleb was thinking.
I asked for your advice in another bug. Why are we continuing to mask qt 4.2? I'd rather just drop support for dbus, like I did. This isn't a hard fix.
