I was calling emerge from su. The variable $PREFIX was defined by the user calling su. Reproducible: Always Steps to Reproduce: 1.create a variable called $PREFIX and assign it to a directory path 2.su to gain root priveledges 3.emerge dhcpcd -av Actual Results: Installs the executable dhcpcd into $PREFIX/sbin Expected Results: For executable to be installed in /sbin I've been trying to see if may be PREFIX is a reserved variable by Gentoo or portage but I'm not finding that anywhere. Also, I emerged other packages while having this $PREFIX variable defined as such and have not had emerge install the binaries or files in my prefix. To fix, I simply renamed the variable and emerge installed into the correct directory.
Prefix uses EPREFIX, not PREFIX. EPREFIX is blacklisted by Portage, so it cannot bleed in from the environment.
Assigning to proper maintainer. Removing prefix@g.o
Roy, there appears to be an issue with dhcpcd's configure script. If PREFIX is set in the environment and --prefix= is given on the command line, the environment setting of PREFIX is used, instead of the --prefix= setting on the command line. For example, if I run: PREFIX=/foo/bar ./configure --prefix=/home/william the configure script ignores the --prefix=/home/william command line switch and uses /foo/bar as the value for PREFIX. Thanks, William
Should be fixed here: http://roy.marples.name/cgi-bin/gitweb.cgi?p=dhcpcd.git;a=commitdiff;h=791c63ac688169ed7d0b4145dfefb2ce0c9cc7d4 Can someone test it?
Roy, I ran the same test I mentioned above, and it works as expected, the --prefix setting is now preferred. Should I cherry-pick the patch or are you going to do another release soon? William
Cherry pick it as the next release won't be for a week or so.
This is fixed in dhcpcd-6.0.2.
