Re: The trigger in your Debian packages
Raphael Hertzog [2011-06-03 10:24 +0200]:
> 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?
postgresql-common: No. This sets up available spell
directories for postgresql-X.Y, but this is more a "cherry on top"
than a core feature. p-common itself as well as existing PostgreSQL
clusters run fine without, and it's not timing sensitive at all.
cracklib is similar: No. It triggers on /usr/share/dict/ wordlists and
updates its hashtables. It is important that the trigger does happen,
but it's not important that it couts as not configured until the
> 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?
N/A for my two packages.
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)