On 08/07/2015 14:53, Peter Humphrey wrote: > It's my turn to seek help understanding portage. > > Yesterday my daily update required a reinstallation of kdelibs with the > nepomuk flag switched on, and that pulled in nepomuk-core and nepomuk-widgets. > But according to equery, those three packages have only a conditional > dependence on nepomuk: > > prh@wstn ~ $ equery d nepomuk-core > * These packages depend on nepomuk-core: > kde-base/kactivities-4.13.3 (nepomuk ? > >=kde-base/nepomuk-core-4.13.3:4[aqua=]) > kde-base/kdelibs-4.14.8 (nepomuk ? >=kde-base/nepomuk-core-4.14.3:4[aqua=]) > kde-base/nepomuk-widgets-4.14.3 (>=kde-base/nepomuk-core-4.14.3:4[aqua=]) > kde-base/plasma-workspace-4.11.19 (nepomuk ? > >=kde-base/nepomuk-core-4.11.19:4[aqua=]) > prh@wstn ~ $ emerge --info | grep nepomuk > prh@wstn ~ $ equery d nepomuk-widgets > * These packages depend on nepomuk-widgets: > kde-base/kdelibs-4.14.8 (nepomuk ? >=kde-base/nepomuk-widgets-4.14.3:4[aqua=]) > > Nepomuk doesn't appear in emerge --info, so why does portage insist that > kdelibs requires nepomuk? > > # emerge -cv nepomuk-widgets nepomuk-core > > Calculating dependencies .... done! > kde-base/nepomuk-core-4.14.3 pulled in by: > kde-base/kdelibs-4.14.8 requires >=kde-base/nepomuk-core-4.14.3:4[-aqua] > kde-base/nepomuk-widgets-4.14.3 requires > >=kde-base/nepomuk-core-4.14.3:4[-aqua] > > kde-base/nepomuk-widgets-4.14.3 pulled in by: > kde-base/kdelibs-4.14.8 requires > >=kde-base/nepomuk-widgets-4.14.3:4[-aqua] > > The version of kdelibs has not changed recently, nor have I made changes to > make.conf or package.use. > > Something odd is going on.
What state is the machine in now? Did you enable the flag and do what portage asks, or is that update still pending? I have a hunch the cause is not kdelibs directly, but rather another package that depends on kdelibs[nepomuk]. If your update is still pending, we can easily find out why with emerge -t -- Alan McKinnon alan.mckin...@gmail.com
