net-misc/dhcpcd:0 -r-xr-xr-x root:root /sbin/dhcpcd net-misc/dhcpcd:0 -r--r--r-- root:root /usr/share/man/man5/dhcpcd.conf.5.lz net-misc/dhcpcd:0 -r--r--r-- root:root /usr/share/man/man8/dhcpcd.8.lz net-misc/dhcpcd:0 -r--r--r-- root:root /usr/share/man/man8/dhcpcd-run-hooks.8.lz See the tracker for more complete explanation of issues with files not writeable by owner.
I disagree with this being a bug - the files are installed like that by design. I'm surprised the file in /lib/dhcpcd (or /libexec) didn't come up either as they are installed without the write bit set as well. If you must go down this route, change the ebuild by setting BINMODE, NONBINMODE, MANMODE and CONFMODE to whatever 0XXX mode you want during the install phase.
I would really appreciate if people followed common patterns rather than invented their own fancy stupid designs that break stuff for no good reason.
(In reply to Michał Górny from comment #2) > I would really appreciate if people followed common patterns rather than > invented their own fancy stupid designs that break stuff for no good reason. That depends on your perspective. The dhcpcd install pattern matches what the BSD's do. To me, that is the common pattern.
And on a another node, dhcpcd uses the common variables BINMODE and others as noted above. So it's possible this could be set maybe in a profile and not in the ebuild. I would imagine there are other packages that use a BSD based install so they would automatically benefit as well. I don't know if GNU tools work with the standard BSD variables or not.
