Summary: | portage ebuild installs relative symbolic links rather than absolute ones | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Eugene St Leger <grimrc> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Eugene St Leger
2006-11-27 17:48:35 UTC
This is by design, absolute symlinks create other problems. I'd recommend you get rid of that symlink and properly mount the partition at the right location. each type has pro/cons, but generally with other packages we've been changing from relative to absolute symlinks when crossing certain path boundaries however, it's assumed that you can use relative symlinks when working within the /usr subdir as the bin/lib/share subdirs should all be on the same partition: /usr/bin/foo -> ../lib/foo (OK) /usr/lib/bar -> ../bin/bar (OK) /usr/lib/meow -> ../share/meow (OK) /usr/bin/boo -> ../../bin/boo (not OK) rather than using a symlink for /usr/bin, a bind mount would work better with minimal effort on your end |