#include <hallo.h>
* Frank Küster [Mon, Mar 13 2006, 07:28:42PM]:
> Eduard Bloch <[EMAIL PROTECTED]> wrote:
>
> >> dpkg-hook /usr/lib/man/update-manpages - run only once in total
> >> dpkg-hook --on-depends foobar ldconfig - run once before depends of foobar
> >
> > What is a depends? Do you mean dependency or dependents?
>
> I think he means dependents: If package foo depends on library foobar,
> dpkg/apt can unpack and configure-without-ldconfig all packages that
> don't depend on foobar, but it must run ldconfig before any package that
> declares: "Depends: foobar" is configured.
Okay... but why? If the cache is not updated, the library package is
still useable, just the lookup will take an insignificant bit longer.
And this functionality would require integration into dpkg.
> > Further, I would not depend on package installation operations but
> > instead invent something like "dpkg-hook --execute ldconfig" to run
> > outstanding tasks noted under the name "ldconfig".
>
> This I don't understand...
Let's rename it to --run-pending.
dpkg-hook --run-pending foobar [ --add-option ... ] - run this command
with optional options. If this task is already in the list, the new
command is executed (together with previous options) and then the task
is removed from the list.
> > That's all. IMO a matter of few hours to implement and test (in Perl).
>
> *And* it's a matter of setting up a good policy which hooks will be
> implemented/allowed. The problem is that if anything goes wrong when
> executing a postponed command, dpkg has no way to tell which package
> caused the failure, and all packages involved will be marked as
> configured fine, while in fact they may be non-functional.
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).
> Therefore it is crucial that only commands
>
> - that cannot sensibly be assumed to fail, und any circumstances
> including f'cked up filesystems,
>
> - or that can safely be assumed to exit with a clear,
> user-understandable error message
>
> can be allowed. Remember, the *user* has to decide what to do, and
> against which package a bug should be filed.
First, if dpkg-hook is implemented as above, it is up to the maintainer
to decide whether to use that feature or not. 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)
Eduard.
--
Marcus Cole: I am a Ranger! We walk in the dark places no others may enter! We
stand on a bridge, and no one may pass. We live for the One! We DIE for the
ONE!
-- Quotes from Babylon 5 --
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
