What are the best practices for handling app-local dynamically loaded libraries? Case in point: sblim-sfcb https://bugzilla.redhat.com/show_bug.cgi?id=466183 This has a bunch of .so files, specific application features, which it calls with dlopen() as those features become used. Current packaging has these all dumped into %{_libdir}/ which seems wrong to me. IMHO they belThis ong in %{_libdir}/%{name}/, and rather than add to /etc/ld.so.conf.d/, the application should simply dlopen() them from that directory directly. It appears this is what apache does. As a follow-on, should this same mechanism be used for plugin .so libs? Does it make sense to include something about this in the guidelines? Thanks, Matt -- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
