I think that equery depends should be useful for finding out why a package is on the system, and not removed by emerge depclean. Therefore, if the package passed to equery depends is in the worldfile, the user should be told this fact. It would be even better if the exact pattern in world and the line number were dumped. Workaround: after EVERY equery depends, run grep -n $PKG /var/lib/portage/world (with the package base name, not the argument to equery depends if it has a version number) Reproducible: Always Steps to Reproduce: (assuming gentoolkit is installed) equery depends gentoolkit Actual Results: colinux-penn ~ # equery depends gentoolkit [ Searching for packages depending on gentoolkit... ] colinux-penn ~ # grep -n gentoolkit /var/lib/portage/world 60:app-portage/gentoolkit colinux-penn ~ # Expected Results: colinux-penn ~ # equery depends gentoolkit [ Searching for packages depending on gentoolkit... ] [ Listed in /var/lib/portage/world line 60 as app-portage/gentoolkit ] colinux-penn ~ #
This bug is 4 years old. Let's close it or act on it. I personally don't think "depends" is the most intuitive place to display this information. $ equery d List all direct dependencies matching a given query Doesn't seem to fit.
Based on how emerge --depclean considers the world and system sets to be dependencies, it makes since to have equery depends also show those dependencies. My thought is to show @world or @system followed by the atom that is in the world or system set. For example: Currently on my system: # equery depends virtual/editor * These packages depend on virtual/editor: app-admin/sudo-1.8.1_p2 (virtual/editor) would become: # equery depends virtual/editor * These packages depend on virtual/editor: app-admin/sudo-1.8.1_p2 (virtual/editor) @system (virtual/editor)
