Re: Changes in handling library dependencies
>>>>> "Mark" == Mark Baker <mbaker@iee.org> writes:
Mark> On Thu, Jan 20, 2000 at 03:34:29PM +0100, Ronald van Loon
Mark> wrote:
>> program needs on the command line. While it may be true that it
>> is sufficient to be *dependent* only on imlib, it is still
>> necessary to specify all those other implicit libraries to the
>> linker. The linker is not smart enough to follow all
>> dependencies that stem from linking to a library.
Mark> Other people have already pointed out that this isn't true.
I remain unconvinced that it is possible to generate this
inter-library dependency information for different libraries within
the same source package where libtool is used. I am still hoping
somebody will prove me wrong, with a satisfactory way of doing this
that doesn't break other libtool features.
Even if a new libtool version fixed these problems, it would be a
while before everyone could use it.
In addition, I think it is a bad idea to assume that all libraries
from the one source package will end up in the one Debian package.
Consider heimdal for example. It has a library, libroken, that its
upstream authors are considering moving into a seperate source
package. What if I wanted to beat the gun, and put the binaries into a
seperate package first? ie so you can install libroken without the
rest of heimdal-lib, for other applications that may benifit from this
library? How would libs from heimdal-lib depend on libroken?
--
Brian May <bam@debian.org>
Reply to: