Hello, I don't really understand how qfile -o is suppose to work and I don't see it documented anywhere. I think there is a bug hidden in here, somewhere. % pwd /etc % qfile -o /etc/localtime /etc/localtime % qfile -o localtime % % qfile --version portage-utils-0.3.1: compiled on Jun 30 2010 So, why does it matter if I use the FULL path or not? And what is the correct answer? Is it orphaned or not? % find /var/db/pkg/ -name CONTENTS |xargs grep localtime|grep etc %
same behaviour with portage-utils-0.5: compiled on Mar 17 2011 $Id: qfile.c,v 1.57 2011/03/02 02:41:08 vapier Exp $ This behaviour makes sense though, because when used like "qfile -o /etc/*" it lists all orphaned files. Might need some doc updates though if it is intended that way.
yes, `qfile -o <file>` should list <file> if it is orphaned the implicit relative path sounds like a bug, but i'd have to look deeper
Not sure if I should open a new bug report, but "qfile -o" seems to be broken for me: Ion ~ # qfile --version portage-utils-0.6: compiled on Oct 19 2011 $Id: qfile.c,v 1.58 2011/10/02 22:08:49 vapier Exp $ file written for Gentoo by <solar and vapier @ gentoo.org> Ion ~ # qfile -o /usr/lib64/xorg/modules/extensions/libdri.so /usr/lib64/xorg/modules/extensions/libdri.so Ion ~ # equery b /usr/lib/xorg/modules/extensions/libdri.so * Searching for /usr/lib/xorg/modules/extensions/libdri.so ... x11-base/xorg-server-1.10.4-r1 (/usr/lib64/opengl/xorg-x11/extensions/libdri.so) It is also return false results when dealing with symlinks: Ion ~ # qfile -o /usr/lib/libGL.so /usr/lib/libGL.so Ion ~ # ls -la /usr/lib/libGL.so lrwxrwxrwx 1 root root 32 Окт 19 00:26 /usr/lib/libGL.so -> opengl/xorg-x11/lib/libGL.so.1.2 Ion ~ # equery b /usr/lib/libGL.so * Searching for /usr/lib/libGL.so ... media-libs/mesa-7.11 (/usr/lib64/opengl/xorg-x11/lib/libGL.so.1.2) Ion ~ # qfile -o /usr/lib64/opengl/xorg-x11/lib/libGL.so.1.2 None returned with the last command (as expected).
file a new bug
(In reply to comment #0) the qfile(1) man page covers how the orphans option works (In reply to comment #2) yes, relative paths are broken. "localtime" ends up matching the basename of "/usr/share/zoneinfo/localtime" which is installed by timezone-data.
http://sources.gentoo.org/gentoo-projects/portage-utils/qfile.c?r1=1.63&r2=1.64