This is a request regarding "fowners" and "fperms". Example ebuild phase: src_install(){ fowners foo:bar /folder/test.txt } Let's assume we have already an existing /folder/test.txt with foo2:bar2 as owner/group. After merging, the group and owner of /folder/test.txt has not changed (That is good, cause I don't want to change it automatically). But there was no warning, that permissions might be wrong. Portage should parse the ebuild for fowners/fperms, check the permissions of the files fowners/fperms is used after the merge and warn you about possibly wrong permissions.
This could be a nice feature to have, at least until bug 396153 gets fixed. There's no need to parse fowners/fperms calls in the ebuild, since we can simply compare the permissions of the directories inside the install image (referred to as ${D} inside ebuilds).
