1 |
On Saturday 04 March 2017 10:52:57 Mick wrote: |
2 |
> On Saturday 04 Mar 2017 09:45:28 Peter Humphrey wrote: |
3 |
> > Greetings. |
4 |
> > |
5 |
> > This is a KDE ~amd64 box, which still depends on kde-apps/kdepimlibs:4 for |
6 |
> > many things. I've been running happily on =app-crypt/gpgme-1.5.5, but |
7 |
> > today |
8 |
> > portage wants to upgrade to =app-crypt/gpgme-1.8.0-r2. But that version |
9 |
> > can't be installed while kdepimlibs:4 is still around, as I see from the |
10 |
> > ebuild: |
11 |
> > |
12 |
> > [...] |
13 |
> > RDEPEND="${COMMON_DEPEND} |
14 |
> > |
15 |
> > cxx? ( |
16 |
> > |
17 |
> > !kde-apps/gpgmepp |
18 |
> > !kde-apps/kdepimlibs:4 |
19 |
> > |
20 |
> > )" |
21 |
> > |
22 |
> > [...] |
23 |
> > |
24 |
> > Is it even possible to satisfy that condition? |
25 |
> |
26 |
> I saw Peter's post just as I hit sent on mine. :-) |
27 |
> |
28 |
> Apparently USE="-cxx -qt5" should allow gpgme to build. kdepimlibs goes |
29 |
> away on KDE-5 and the packages affected are in flux at this point. I will |
30 |
> rinse and repeat at a later date. |
31 |
|
32 |
True, but then you'll probably hit bug #600510. I did and ended up going the |
33 |
mask route for now. (I may actually attempt to upgrade to KDE PIM 16.12.2, but |
34 |
that pulls in a long tail of other packages due to QT_MINIMAL="5.7.0".) |
35 |
|
36 |
-- |
37 |
Marc Joliet |
38 |
-- |
39 |
"People who think they know everything really annoy those of us who know we |
40 |
don't" - Bjarne Stroustrup |