On Fri, Jul 11, 2008 at 02:40:07PM -0400, Joey Hess wrote:
> Bill Allombert wrote:
> > Could you tell me what means 'triggers-awaited' and how I should handle
> > it ?
>
> The triggers.txt says:
>
> At a trigger activation, the interested packages(s) are added to the
> triggering package's list of triggers-awaited packages; the triggering
> package is said to await the trigger processing.
>
> A package which has pending triggers, or which awaits triggers, is not
> considered properly installed. There are two new dpkg status values,
> `triggers-pending' and `triggers-awaited', which lie between
> `config-failed' and `installed'.
>
>
> The purpose of the check in update-menus, AIUI, is to package(foo)
> test in a menu file not enable the menu if the package is removed.
>
> Which I suppose must only be needed in the uncommon case where a menu file
> needs a package other than the package containing it to be installed, or
> where the menu file is left behind after package removal as a conffile
> might be.
>
> So, it seems this check is still needed when --triggered. But,
> it should be safe, I think, to check for the triggers-awaited state and
> treat is as equivilant to "installed". It should likewise do the same
> with the "triggers-pending" state; a package could have both
> triggered menu and been itself triggered, and then it would be in the
> latter state.
Thanks, I agree with your analysis.
> PS, it looks to me like the handling of the installed_packages string,
> which just gets a list of installed packages shoved into it with no
> delimiters, is a bit problimatic. Specifically, if "foobar" is added to
> the string, a test is_pkg_installed("foo") will succeed, won't it?
installed_packages is not a string but a set of string, so this should
be fine:
set<string> installed_packages;
Cheers,
--
Bill. <[EMAIL PROTECTED]>
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
