Re: Semantic change for dpkg triggers?
On 6/2/2011 8:33 AM, Ian Jackson wrote:
In general, the reason for this rule about satisfying dependencies is
that a triggering package may well not be functional at all until the
trigger is run. For example, if the triggering package T needs to be
registered with the interested package I, a package D which depends on
T may find that T does not work - and D's postinst may fail due to T
If postinst depends on the package, then it should be a pre-depend, not
a depend, shouldn't it?