On Fri, 22 Jun 2007 13:03:53 -0400, Jesse Keating wrote: > The question I have is why can't we teach the provides finder to be smarter > about things that are outside the standard path? Why fix this in N* packages > instead of the source? Good question. ;) How many packages benefit from automatic Prov/Req for libraries they store outside default run-time linker's search path? Is it just a few huge application suites, which alter the linker's search path at run-time to point it to many private libs? How many packages use LD_LIBRARY_PATH, RPATH, or ld.so.conf.d files? Are there inter-package dependencies for library sonames in private paths? [...] Two example bugs of where the "Provides" cause a real conflict: https://bugzilla.redhat.com/245323 (libmd5.so.0) https://bugzilla.redhat.com/245326 (libsqlite.so.0) -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
