In src_install(), the links created from /bin/?? to /usr/bin/?? are created within /usr/bin with "ln -s ../../bin/*". This caused a problem since my /usr is actually a symbolic link to elsewhere. This threw off the ../../bin assumption. Is there any reason /bin could not be hardcoded? Reproducible: Always Steps to Reproduce: Move /bin to a nonstandard location and replace with a symbolic link. Emerge coreutils Actual Results: Dead links in /usr/bin. Emerge no longer worked since it referenced a broken /usr/bin/env link. Expected Results: Link to /bin instead of ../../bin
Description not quite right. My /usr is actually the dir in the nonstandard location, link to /usr. This is what caused the ../../bin to be incorrect.
To reproduce, move /usr to nonstandard location and link to /usr. emerge coreutils.
It is the standard way to do things (using relative symlinks), as it is supposidly more 'secure' than absolute symlinks. Have you done a: $ ls -l /usr/X11R6/lib/X11/ lately ? My take on this is that it is really a non-standard setup, and complicates things too much - rather then use bind-mounts to get what you want. Seemant?
we don't support symlinking /usr and /bin to non-standard locations. Like Az said, you're better off bind mounting.
