Summary: | app-portage/gentoolkit: equery depends does not display || dependencies | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | aditsu <aditsu> |
Component: | Current packages | Assignee: | Portage Tools Team <tools-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge -pv --depclean &> verbose.log |
Description
aditsu
2011-08-05 15:25:24 UTC
See `man emerge` for --with-bdeps. This is normal behavior for buildtime-only depends (DEPEND) to get pruned from system, unrequired at runtime (RDEPEND) Thanks for the explanation, but man emerge says: This defaults to [...] ´y´ for the --depclean action, meaning they will not be removed Also, x11-misc/icon-naming-utils (and gnome-icon-theme too) was listed in both "emerge -cp --with-bdeps n" and "emerge -cp --with-bdeps y" Oh, and I have portage 2.1.10.3 (In reply to comment #0) > # equery d gnome-icon-theme > * These packages depend on gnome-icon-theme: > app-text/evince-2.32.0-r3 (>=x11-themes/gnome-icon-theme-2.17.1) The equery output seems somewhat incomplete. The actual dependency of the ebuild looks like this: || ( >=x11-themes/gnome-icon-theme-2.17.1 >=x11-themes/hicolor-icon-theme-0.10 ) This means that gnome-icon-theme is eligible for removal if you have hicolor-icon-theme installed. If that's not the cause of the issue, the please attach verbose depclean output: emerge -pv --depclean &> verbose.log Created attachment 282223 [details]
emerge -pv --depclean &> verbose.log
I gave the complete output of "equery d gnome-icon-theme".
Here I'm attaching the output of "emerge -pv --depclean &> verbose.log"
Indeed, the ebuild dependency is as you said. That means the equery output is misleading? (In reply to comment #4) > (In reply to comment #0) > > # equery d gnome-icon-theme > > * These packages depend on gnome-icon-theme: > > app-text/evince-2.32.0-r3 (>=x11-themes/gnome-icon-theme-2.17.1) > > The equery output seems somewhat incomplete. The actual dependency of the > ebuild looks like this: > > || ( >=x11-themes/gnome-icon-theme-2.17.1 >=x11-themes/hicolor-icon-theme-0.10 > ) > > This means that gnome-icon-theme is eligible for removal if you have > hicolor-icon-theme installed. Your debug output confirms the above explanation: x11-themes/hicolor-icon-theme-0.12 pulled in by: app-text/evince-2.32.0-r3 kde-base/kdebase-data-4.7.0 media-gfx/gimp-2.6.11-r1 So, if you want to keep x11-themes/gnome-icon-theme and its dependencies (such as x11-misc/icon-naming-utils), you'd better add it to your world file: emerge --noreplace x11-themes/gnome-icon-theme (In reply to comment #6) > Indeed, the ebuild dependency is as you said. That means the equery output is > misleading? The dependency is ambiguous, so the information is correct but doesn't give a complete picture. I'll reassign to tools-portage in case they want to do something about that. Maybe there's already an option for that, I don't know. I don't need to keep gnome-icon-theme or icon-naming-utils, I don't even really know what they are, I just thought they would break evince. Let's see if equery can be improved. |