1 |
It's my turn to seek help understanding portage. |
2 |
|
3 |
Yesterday my daily update required a reinstallation of kdelibs with the |
4 |
nepomuk flag switched on, and that pulled in nepomuk-core and nepomuk-widgets. |
5 |
But according to equery, those three packages have only a conditional |
6 |
dependence on nepomuk: |
7 |
|
8 |
prh@wstn ~ $ equery d nepomuk-core |
9 |
* These packages depend on nepomuk-core: |
10 |
kde-base/kactivities-4.13.3 (nepomuk ? >=kde-base/nepomuk-core-4.13.3:4[aqua=]) |
11 |
kde-base/kdelibs-4.14.8 (nepomuk ? >=kde-base/nepomuk-core-4.14.3:4[aqua=]) |
12 |
kde-base/nepomuk-widgets-4.14.3 (>=kde-base/nepomuk-core-4.14.3:4[aqua=]) |
13 |
kde-base/plasma-workspace-4.11.19 (nepomuk ? >=kde-base/nepomuk-core-4.11.19:4[aqua=]) |
14 |
prh@wstn ~ $ emerge --info | grep nepomuk |
15 |
prh@wstn ~ $ equery d nepomuk-widgets |
16 |
* These packages depend on nepomuk-widgets: |
17 |
kde-base/kdelibs-4.14.8 (nepomuk ? >=kde-base/nepomuk-widgets-4.14.3:4[aqua=]) |
18 |
|
19 |
Nepomuk doesn't appear in emerge --info, so why does portage insist that |
20 |
kdelibs requires nepomuk? |
21 |
|
22 |
# emerge -cv nepomuk-widgets nepomuk-core |
23 |
|
24 |
Calculating dependencies .... done! |
25 |
kde-base/nepomuk-core-4.14.3 pulled in by: |
26 |
kde-base/kdelibs-4.14.8 requires >=kde-base/nepomuk-core-4.14.3:4[-aqua] |
27 |
kde-base/nepomuk-widgets-4.14.3 requires >=kde-base/nepomuk-core-4.14.3:4[-aqua] |
28 |
|
29 |
kde-base/nepomuk-widgets-4.14.3 pulled in by: |
30 |
kde-base/kdelibs-4.14.8 requires >=kde-base/nepomuk-widgets-4.14.3:4[-aqua] |
31 |
|
32 |
The version of kdelibs has not changed recently, nor have I made changes to |
33 |
make.conf or package.use. |
34 |
|
35 |
Something odd is going on. |
36 |
|
37 |
-- |
38 |
Rgds |
39 |
Peter |