I emerged licq-1.2.0a-r2, but it failed because it couldn't find /usr/lib/licq/licq_qt-gui.so. In fact, there was just a file called licq_kde-gui.so, so I symlinked licq_qt-gui.so -> licq_kde-gui.so and now it works fine. Don't know who's the culprit, the ebuild script or the Makefile, but anyway the workaround is rather trivial.
I also symlinked licq_qt-gui.la -> licq_kde-gui.la, BTW.
please post the output of 'emerge info'.
Created attachment 6708 [details] emerge info output
I just emerged licq and I have the same problem too. -- Stephen
I've committed an licq-1.2.4-r1 which creates the symlinks automatically when needed. Please test.
got a better solution for it ... i'll reassign it to me (if anyone minds feel free to take it back) ;)
changing default (initial) config
should work ok now
closing
Bug #17414 was opened recently and appears to duplicate this bug; I suggest adding / modifying the short_desc field to include "QT GUI symlink KDE" or similar to make this bug easier to find. Would it be possible to include logic in the ebuild to use either the KDE *OR* the QT GUI? (They are similar, but not identical) ie; in the case where QT is enabled, but KDE is not, build the QT gui instead of the KDE GUI? People using WindowMaker, for example, will have minor difficulties (primarily with the "Dock Icon") when using the KDE GUI in a QT-only environment.
*** Bug 17414 has been marked as a duplicate of this bug. ***
see last comment .. (kde)
OK, this has been fixed in 1.2.6. The USE variables are now working right. Before, the eclass inherit statement was in a conditional and this was causing b0rkage in the dep cache, causing weird or unwanted dependencies in conjunction with USE vars.
