Re: Bug#80560: -l<directory> option to dh_shlibdeps still needed
On Fri, 29 Dec 2000, Steve Langasek wrote:
> 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.
Nononononono. You are confused.
LD_LIBRARY_PATH is used so that programs and libs in debian/tmp that are
compiled AGAINST libs in debian/tmp can be properly resolved with ldd.
debian/shlibs.local is then used to map the libraries to packages.
debian/shlibs.local can be used to override the system
(/var/lib/dpkg/info/*.shlibs) shlibs files.
There are 2 things going on, and both are needed.
----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-----END GEEK CODE BLOCK-----
----BEGIN PGP INFO----
Adam Heath <doogie@debian.org> Finger Print | KeyID
67 01 42 93 CA 37 FB 1E 63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----
Reply to: