Re: [Pkg-octave-devel] The trigger in your Debian packages
On Fri, Jun 03, 2011 at 10:24:23AM +0200, Raphael Hertzog wrote:
> 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.
> To make it easier to find the packages that concerns you, I have put a
> dd-list below.
> Thanks for your help!
Answering for the two groups/persons below; Octave only uses 'interests'
> Debian Octave Group <email@example.com>
> Thomas Weber <firstname.lastname@example.org>
> octave3.2 (U)
Producers of our triggers are packages that drop their files in one of
Octave's paths. In order to know about these files, Octave keeps a cache
which must be updated upon installation -- without it, Octave will not
look for these files.
So, sorry, but unless the trigger is run, these packages cannot be taken
as 'configured' -- the Octave interpreter will not know about them.