Portpeek reads certain Portage-related config files that reside in /etc, but when searching for them, it does so from the current-working directory. For example, if you run it from your home directory, it'll fail. But if you cd into '/', it'll run successfully. This is not stable behavior, and its ebuild should be masked. However, this problem seems to have been fixed in version 1.5.8.4 (which is currently masked). Reproducible: Always Steps to Reproduce: 1. emerge app-portage/portpeek-1.5.7.2 2. cd into your home folder, and run 'portpeek --all' 3. cd into your root directory, and run it again Actual Results: It complains with: Could not find file etc/portage/package.keywords Expected Results: It should be able to run successfully, no matter what directory you're currently in.
as soon as amd64 stabilizes 1.5.8.4 this version will be killed. See bug #309059
This version has been removed from the tree as 1.5.8.4 has been stabilized in bug #309059.