Bug#447609: ldconfig triggerisation
On Tue, Oct 23, 2007 at 11:11:37AM +0100, Ian Jackson wrote:
> Unfortunately because of the way /lib and particularly /usr/lib are
> dumping grounds, file triggers wouldn't work properly. A file trigger
> is activated by packages' files whose pathnames start with the name of
> the trigger. So the trigger would have to be /usr/lib/ but that
> covers enormous amounts of junk.
Why not just move to use of dpkg-trigger piecemeal in each postinst?
That would involve no more invocations of ldconfig than we are already
enduring.
Reply to: