On Mon, Mar 29, 2021 at 2:36 PM Charalampos Stratakis <cstratak@xxxxxxxxxx> wrote:
----- Original Message -----
> From: "Alexander Bokovoy" <abokovoy@xxxxxxxxxx>
> To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx>
> Sent: Friday, March 26, 2021 10:06:28 PM
> Subject: Re: Proposal to fail builds if RPATH is found in Fedora 35
>
<snip>
> For example, Samba has a number of internal libraries in
> /usr/lib64/samba which have to be linked to by any plugin built for
> Samba, even when it is provided by a different package. This situation
> is not described in the packaging guidelines and practically ignored.
Thanks for this example, I'll investigate that specific usecase.
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.
(Sorry if this has already been discussed, I'm a bit behind on email.)
--
Kalev
_______________________________________________ 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
