Re: Delayed ldconfig execution in postinst step

[Frank Küster <frank@debian.org>]

Eduard Bloch <edi@gmx.de> wrote:

> Ehm... all the time I talk about non-critical things! Dealing with
> success checking in merged commands would be insane, we cannot assign
> the failure to a certain package (except when there is just one, of
> course).
>
[...]
> First, if dpkg-hook is implemented as above, it is up to the maintainer
> to decide whether to use that feature or not. 

And maintainers can err.  Or be overly bold in "trying out" things.
I've seen commands fail in my own postinst scripts that I would never
have imagined...

> Second, the command
> handler can print meaningfull messages (maybe abbreviating for
> large list of packages):
>
> Executing pending tasks:
>     ldconfig (requested by libfoo, libbar, libbaz)
>     menu-update (requested by 23 packages, see dpkg.log for details)

I wouldn't be surprised if a "proper" combination of a buggy menu or
menu-methods file and a buggy menu-update could lead to funny
failures...  But you are right, if it is done well, with status messages
as you indicated, it would be a great help.

Regards, Frank
-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)