I know this isn't supported usage, but it looks like something has really gone off the rails here: $ equery uses alsa [ Searching for packages matching alsa... ] [ Colour Code : set unset ] [ Legend : Left column (U) - USE flags from make.conf ] [ : Right column (I) - USE flags packages was installed with ] [ Found these USE variables for sys-kernel/gentoo-sources-2.6.21-r4 ] U I - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1] - - symlink : Force kernel ebuilds to automatically update the /usr/src/linux symlink. [ Found these USE variables for sys-kernel/gentoo-sources-2.6.22-r5 ] U I - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1] - - symlink : Force kernel ebuilds to automatically update the /usr/src/linux symlink. [ Found these USE variables for sys-kernel/gentoo-sources-2.6.22-r2 ] U I - - build : !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for creating build images and the first half of bootstrapping [make stage1] - - symlink : Force kernel ebuilds to automatically update the /usr/src/linux symlink.
Actually, that output is correct. 'alsa' matches virtual/alsa, which when expanded matches sys-kernel/gentoo-sources. You can see the same behavior from the emerge command if you do an 'emerge -pv alsa' Even though I agree that the output seems strange, since it was a valid package name, there is nothing that I can fix.