maybe I'm missing something here? it seems that all *.eclass-files are not owned by any package (checked with epm v0.8.4 and etcat). (/usr/portage/eclass/ belongs to baselayout but the contents is "owner-less") Reproducible: Always Steps to Reproduce:
The eclasses are created/updated with emerge sync, so they don't belong to any package. The same is true for the whole /usr/portage tree.
many packages use /usr/portage/eclass/*.eclass ... the way you check is if an ebuild has 'inherit <eclass>' in it
Argh! Right, everything is /usr/portage is synced and can't belong to a package. A little history what led me off the track: I was locking for the *.eclass files and listed the contents of "sys-apps/portage" -- but (suprise-suprise) no eclass-files in there. At that point I stopped thinking, ran "locate" to find the eclassed, checked what package they belong to, ... :| It seems that I can't "RESOLVE" this bug -- maybe some bugzilla-ghost can help? ;)
np ;)