Bug#447609: ldconfig triggerisation
Daniel Jacobowitz writes ("Re: Bug#447609: ldconfig triggerisation"):
> On Tue, Oct 23, 2007 at 11:11:37AM +0100, Ian Jackson wrote:
> > > The only failure case I can think of would be a package which places
> > > libraries in the multi-arch directories, which Debian locates using a
> > > file in /etc/ld.so.conf.d, and the same or another package which runs
> > > a newly installed program using the library from the first package
> > > in its postinst.
> >
> > Do such packages typically invoke ldconfig in the same way as a normal
> > package does ? If not then we could distinguish the two kinds of
> > ldconfig call.
>
> I don't think there would be any difference.
Hrm. That's troublesome. Can we insist on them making such a
different invocation ?
If we can't then the ldconfig provided by glibc can't tell the
difference and AFAICS that means we can't provide the optimisation
without updating all packages.
Ian.
Reply to: