rpm AutoRequires/AutoProvides and dsos not in linker path, do we care ?

[Chuck Anderson]

On Wed, Jun 17, 2009 at 09:42:38AM -0500, Chris Adams wrote:
> Once upon a time, Chuck Anderson <cra at WPI.EDU> said:
> > > b.2) extend the autorequires/autoprovides in some (handwaves) way to
> > > better indicate the desired match
> > 
> > I like this idea better.  AutoReq/Prov should only search system-wide 
> > deafult search paths for .so's, perl modules, and any other such 
> > objects that it supports.
> 
> That breaks things, because a program in /usr/bin may require a module
> or library in a private directory.  You have to search all directories
> for provides to satisfy internal requires.

If a program in /usr/bin requires something in a private, non-system 
directory that is provided by a different package, then the 
provides/requires need to express that somehow, perhaps by using a 
full path in the provides.  Until that becomes possible, I'm inclined 
to say that AutoReq/Prov shouldn't be searching private directories, 
and we should require all packages that have such requirements to use 
manual Requires: on either the file path or the package that provides 
the private library.  Keeping things the way they are now is just 
plain broken.