Yes, that possible ld.so.conf fragment in the buildroot needs to be covered.
But, I think the hosts ld.so.conf[.d] needs to be processed as well. The
currently building package could be installing to a subdirectory that some
other package (which would have to be a build-dependency) has declared a system
path by installing such a fragment.
At the baseline I need a way to determine whether a library in a package we're
building is considered a system library or not.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2872#discussioncomment-8245268
You are receiving this because you are subscribed to this thread.
Message ID:
<rpm-software-management/rpm/repo-discussions/2872/comments/8245...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
