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.
I believe
On 06/03/2011 10:24 AM, Raphael Hertzog wrote:
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 don't use any of the triggers but the one for