Am Donnerstag, den 31.07.2008, 16:46 -0400 schrieb Joey Hess: > Once apt trigger deferral is implemented, all the triggers will run at > the very end of the apt run, which can be quite a long time after the > kernel packages are removed and installed.
What exactly is this apt trigger derral which will be implemented? Luckly I had to do now a apt-get build-dep grub2 and I noticed the man-db trigger is called after every package is extracted and not after the whole apt/dpkg process after everything setting up. And man-db uses just directory triggers which I first thought of. A trigger which runs after every package has been extracted and not yet configured should work fine for us, too. Will apt change something with that or might there be a problem which I currently can't think of with that method? If it works then I/we only need to find a way that update-grub is run on a grub2 update too but only once if there's kernel update too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]