On Wed, 27 Dec 2000, Joey Hess wrote: > Steve Langasek wrote: > > I had thought this was just cosmetic, but that's not the case. If > > LD_LIBRARY_PATH includes the path to the libraries we've just built, it can > > use the respective DEBIAN/shlibs files from the package install directory, > > and > > debian/shlibs.local is no longer necessary.
> Hmm, but isn't debian/shlibs.local the accepted, documented way to do > this? It is the documented way, yes, but based on what I've been told it is no longer the method preferred by the actual dpkg-dev code. dpkg-shlibdeps spits out a warning for libraries not in the path because the authors want *all* the libraries to be in the path, including those that come from the same source package. I think this is reasonable. I think using debian/shlibs.local would also be reasonable, but the decision has already been made in the code which makes LD_LIBRARY_PATH an easier solution. Steve Langasek postmodern programmer
