Kalev Lember wrote:
> I don't think there is anything wrong with having rpath to a private
> directory (/usr/lib64/samba) -- that's exactly what rpath is for, so that
> the app could find its private libraries that we don't want the whole
> world to have access to. What we should avoid is rpath to standard libdir,
> which is /usr/lib or /usr/lib64.
+1
And the reason for that is that having RPATH to a standard libdir breaks
overrides through ld.so.conf.d or LD_LIBRARY_PATH. E.g., the -freeworld
library packages in RPM Fusion (e.g., qt5-qtwebengine-freeworld) (which use
ld.so.conf.d) will NOT work with packages that have RPATH set to the
directory containing the Fedora build of the library.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
