PMS merely says wrt fperms: fperms: Acts as for chmod, but takes paths relative to the image directory. for other programs in this section, it's implied that they take no arguments (although it also does not explicitly state that when it should). the problem is that ebuilds have long used options like -R, and out of order (options after files), so we're to presume that any flag is valid. but then we're tied to a specific chmod implementation (GNU in this case) rather than something more desirable (like POSIX). we should specify the behavior explicitly: * fperms [-R] <permissions> <file> [files] <permissions> may take the form of any POSIX mode string: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/chmod.html#tag_20_17_13
