Bug#68981: dpkg: runs ldconfig way too often
severity 68981 wishlist
reassign 68981 dpkg
thanks
>>"Josip" == Josip Rodin <joy@cibalia.gkvk.hr> writes:
Josip> On Fri, Aug 11, 2000 at 03:44:08PM -0600, Dwayne C. Litzenberger wrote:
>> Post-install ldconfigs should be taken over by dpkg. ldconfig
>> should only be run once at the end of an install, or prior to
>> installing packages that pre-depend on newly-installed libraries.
>> This would substantially reduce install times that are being
>> slowed down by redundant ldconfig calls.
Josip> Since dpkg only runs ldconfigs that are invoked from package
Josip> postinst scripts, the packages would have to changed[1]. That
Josip> would have to become a policy decision first, I think.
Umm. I think we should have a mechanism in place before we
change policy. And we can't just change policy and have all the
packages using ldconfig sudenly become non-compliant; we need to have
a transition strategy, in which we accept that not all packages shall
be transitioned for a period.
Indeed, at a minimu, we need a dpkg that runs ldconfig, or
implements a post install hook mechanism (triggers), or something,
before this becomes a policy issue.
Policy should follow, not ead, a transition like this. Indeed,
we should have a working model/pilot hammered out and tested before
writing policy about it, since the design would well change during
implementation.
I am sending this back to dpkg as a wishlist item
manoj
--
"Committees do harm merely by existing." Freeman Dyson
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: