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