[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: The trigger in your Debian packages



OoO En  cette matinée  pluvieuse du vendredi  03 juin 2011,  vers 10:24,
Raphael Hertzog <hertzog@debian.org> disait :

> Please reply for the packages that you maintain to the question that
> concerns you:

> 1/ If your package uses the "interest" directive in the triggers files,
> is it important that the "triggering" packages that activate your triggers
> be considered as not configured (and thus not satisfying dependencies)
> until the trigger has been processed?

> 2/ If your package uses the "activate" directive, is it important that
> your package be considered as not configured (and thus not satisfying
> dependencies) until the trigger has been processed?


> I have put "no" as answer for the "install-info" and "man-db" packages.
> For the others, I would like you to answer explicitly yes or no with a
> short rationale. If you don't know what to answer, please reply describing
> what your trigger does, and we'll try to find out through discussion.

For "nevow",  both triggers  are here to  rebuild the plugin  cache. The
plugin system  is critical since  most daemons written with  nevow needs
use the plugin system to  start themselves. However, the plugin cache is
not  so important.  If it  is  not updated,  the only  drawback is  some
warning message if the daemon  is started as non-root user. Therefore, I
think the package can be considered as configured without the triggers.
-- 
Vincent Bernat ☯ http://www.luffy.cx

Avoid multiple exits from loops.
            - The Elements of Programming Style (Kernighan & Plauger)

Attachment: pgpts2XqeGbYn.pgp
Description: PGP signature


Reply to: