we goofed
update-menus already has a mechanism to avoid running too many times
from the authors:
>It does not work this way. When update-menus run, it check whether the
>dpkg
>lock is taken. In this case it check if the menu lock is taken. If yes,
>it just quit. if not, it take the menu lock and w
On Thu, Oct 21, 2004 at 10:07:53AM +0200, A Mennucc wrote:
> But I would not do this for ldconfig:
> what if a package needs a library it depends on to configure itself?
Isn't that why library packages must include the .so symlinks, so
they work before ldconfig is called?
--
I tested it and it seems ok; so
I sent the following proposal as a wishlist bug for 'menu'
A Mennucc wrote:
Luke Kenneth Casson Leighton wrote
as an example, 80% of all debian postinst (post install) packages
on my computer result in the running of update-menus.
you don't need to change the whol
Luke Kenneth Casson Leighton wrote
as an example, 80% of all debian postinst (post install) packages
on my computer result in the running of update-menus.
you don't need to change the whole of the packages to implement the above
just add a few diverts, create some specific locks , and check on e
4 matches
Mail list logo
