Summary: | app-portage/portage-utils: qlist -o doesn't work properly | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Coacher <itumaykin+gentoo> |
Component: | Tools | Assignee: | Portage Utils Team <portage-utils> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Coacher
2011-11-26 22:24:14 UTC
This is expected behavior, qfile -o only checks for files created during the emerge process, not ones generated later by things like eselect-mesa. the examples you've posted are symlinks not owned by any pkg that i can see. if you look at the equery output, it's telling you what owns the *destination* of the symlink, not the symlink itself. qfile will tell you what owns the symlink. compare & contrast: $ cd /tmp $ ln -s /bin/ls $ qfile -o /tmp/ls /tmp/ls $ equery /tmp/ls * Searching for /tmp/ls ... sys-apps/coreutils-8.14 (/bin/ls) Thanks for the explanation. It was just my misunderstanding. i might be open to adding an option so people can say "resolve symlinks, and then tell me what owns the file". not sure though. (In reply to comment #4) > i might be open to adding an option so people can say "resolve symlinks, and > then tell me what owns the file". not sure though. That would be great! |