Many distros, including MacPorts, have avoided @rpath usage in their port trees 
except for certain circumstances (relocatable bundles, etc).

It’s hard to know just what library is being found to be used, and it’s hard to 
force a certain one to be used, for one of many reasons why @rpath is avoided.

Debian has written up a full article about why they don’t want to see @rpath 
usage in Debian:

https://wiki.debian.org/RpathIssue

MacPort’s explanations would be similar, if we wrote them all out.

Best, 

Ken

Reply via email to