On Fri, Jun 03, 2011 at 10:24:23AM +0200, Raphael Hertzog wrote:
> Hello,
>
> you're maintaining a Debian package which provides a trigger file.
> Currently a package that "activates" a trigger is put in the
> "triggers-awaited" status where it doesn't fulfill dependencies.
> The trigger must first be processed and only then is the package
> considered as "installed".
> Please reply for the packages that you maintain to the question that
> concerns you:
I maintain the cracklib2 package.
> 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?
cracklib2 is interested in various dictionary files. The files need to
be available in the file system but cracklib2 doesn't care whether the
packages providing the dictionary packages are configured.
So no, it's not important the the packages triggering the "interest"
of cracklib2 are configured.
> 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?
cracklib2 doesn't use the "activate" directive.
Kind Regards,
Jan
--
Jan Dittberner - Debian Developer
GPG-key: 4096R/558FB8DD 2009-05-10
B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD
http://ddportfolio.debian.net/ - http://people.debian.org/~jandd/
Attachment:
signature.asc
Description: Digital signature