On Mon, 22 Sep 2008 08:48:57 +0100 Mick <[EMAIL PROTECTED]> wrote: > Initially portage informed me about: > > [blocks B] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2) > > So, I unmerged <app-crypt/qca-1.0-r3 and emerged > app-crypt/qca-2.0.0-r2. Now it seems kopete won't compile without > app-crypt/qca-1.0-r2: =============================================== > # emerge -upDv kopete > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild NS ] app-crypt/qca-1.0-r2 0 kB > [ebuild N ] kde-base/kopete-3.5.9 USE="addbookmarks alias > autoreplace connectionstatus contactnotes crypt gadu highlight > history irc jingle nowlistening sametime slp sms ssl statistics > texteffect webpresence winpopup xscreensaver > yahoo -arts -debug -groupwise -kdeenablefinal -kdehiddenvisibility > -latex -netmeeting -translator -xinerama" 0 kB > [blocks B ] <app-crypt/qca-1.0-r3 (is blocking > app-crypt/qca-2.0.0-r2) > > Total: 2 packages (1 new, 1 in new slot, 1 block), Size of downloads: > 0 kB =============================================== > > What is the elegant way out of this?
The ssl support in Kopete depends on qca-tls-1*, which pulls qca-1*. So, if you don't need ssl support in Kopete, then you could disable it by: echo 'kde-base/kopete -ssl' >> /etc/portage/package.use -- Best regards, Daniel
