Re: Bug#307488: please upgrade to newer libtool (libtool1.4 being removed)
On Tue, 03 May 2005, Thomas Bushnell BSG wrote:
> > libtool1.4 is no longer maintained and will be removed from the
> > archive after sarge is released. Please upgrade your package to use a
> What about the fact that there are packages which still need it? You
They are broken right now, and will have to be fixed, since libtool
1.4-generated breakage will not be tolerated in etch.
> can't rely on reverse depends, because libtool is often used on the
> developer's system and need not show up on Build-Depends.
We will fix those as we find them during etch. I am sure we will build
quite the upgrading-and-fixing-libtool-builds knowledge base during it, so
it should not be too painful.
I am far more worried with other things we will have to tack heads on, such
as our known difficulty with avoiding fucked up linking of different
incompatible ABIs in the same lib/dso/executable. Things like suddenly
forcing all nss-modules to be incompatible with the very presence of all
libraries with different versions than what they are linked with (until we
deploy symbol versioning in all affected libraries), and so on...
It is not something most users face, as most people live well with no nss
modules loaded at all, but those who do are completely helpless to fix (it
is *impossible* to fix this user-side). Major messes involving libsasl and
libldap come to mind as well...
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot