On Saturday 04 Mar 2017 12:42:38 Alan McKinnon wrote:
> On 04/03/2017 11:45, Peter Humphrey wrote:
> > Greetings.
> >
> > This is a KDE ~amd64 box, which still depends on kde-apps/kdepimlibs:4
> > for many things. I've been running happily on =app-crypt/gpgme-1.5.5,
> > but today portage wants to upgrade to =app-crypt/gpgme-1.8.0-r2. But
> > that version can't be installed while kdepimlibs:4 is still around, as
> > I see from the ebuild:
> >
> > [...]
> > RDEPEND="${COMMON_DEPEND}
> >
> > cxx? (
> >
> > !kde-apps/gpgmepp
> > !kde-apps/kdepimlibs:4
> >
> > )"
> >
> > [...]
> >
> > Is it even possible to satisfy that condition?
>
> No, but you can mask app-crypt/gpgme-1.8.0-r2 and stay on 1.5/1.6
Yes, I've done that, but why has such silliness been allowed out?
I may take the other route and add -cxx (and -qt5?) to USE for gpgme; needs
a little thought.
In answer to Alan, 23 packages here depend on kdepimlibs:4. That's with the
plasma profile, so I'm not being Luddite here. It's not nearly time yet to
ditch :4.
--
Regards
Peter
