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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jun 17, 2009 at 10:50:43PM -0400, Bill Nottingham wrote:
> Chuck Anderson (cra@xxxxxxx) said: 
> > > "system-wide" includes paths mentioned in /etc/ld.so.conf.d/*, which are
> > > files provided by other packages.  Suddenly your search scope is
> > > unbounded again.
> > 
> > Not really unbounded.  If a package puts a file in /etc/ld.so.conf.d/ 
> > then the library is now available system-wide, so it should be 
> > searched by autorequires/autoprovides.
> 
> The package that puts the file in ld.so.conf.d and the package that
> puts libraries into the location specified in that file may not be
> the same package, and actually may have no dependencies between
> them at all...

Do we have any examples of that?  I'd be inclined to say if there are 
a very few cases where one package provides an ld.so.conf.d file that 
ends up being used by many other packages, we should just put that 
path into the system default /etc/ld.so.conf, so it is always present.

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux