Josselin Mouette writes ("Re: Triggers in menu"):
> Le mercredi 04 juin 2008 à 16:33 -0400, Joey Hess a écrit :
> > The current triggers code does not call the triggered script each time a
> > file is touched. The triggered script is called once at the end of the
> &g
Le mercredi 04 juin 2008 à 16:33 -0400, Joey Hess a écrit :
> The current triggers code does not call the triggered script each time a
> file is touched. The triggered script is called once at the end of the
> dpkg run, and once after the set of changed packages are unpacked. (I'm
> not sure why th
On Wed, 4 Jun 2008, Joey Hess wrote:
I definitely doubt that because there is no other explanation for #484167.
Conffiles are not moved into place until package configuration time,
so #484167 is entirely consistent with the latter call I describe
above.
Ah OK, this explains the problem. So
Andreas Tille wrote:
> On Wed, 4 Jun 2008, Joey Hess wrote:
>
>> The current triggers code does not call the triggered script each time a
>> file is touched. The triggered script is called once at the end of the
>> dpkg run, and once after the set of changed packages are unpacked. (I'm
>> not sure
On Wed, 4 Jun 2008, James Vega wrote:
The number of times update-menus is called should be at most as many as
before triggers were introduced.
No. It might be that packages ship more than one file in /usr/lib/menu
and /usr/share/menu and each file there seems to trigger an update-menus
run (e
On Wed, 4 Jun 2008, Joey Hess wrote:
The current triggers code does not call the triggered script each time a
file is touched. The triggered script is called once at the end of the
dpkg run, and once after the set of changed packages are unpacked. (I'm
not sure why the latter call happens.)
I
On Wed, Jun 04, 2008 at 10:06:22PM +0200, Andreas Tille wrote:
> On Wed, 4 Jun 2008, Joey Hess wrote:
>
>> That would prevent update-menus from being run if a package was
>> installed not using apt.
>
> Yes, this is correct. But what is actually the advantage of calling
> update-menus using trigge
Andreas Tille wrote:
> Yes, this is correct. But what is actually the advantage of calling
> update-menus using triggers instead of doing it in the postinst.
> I always assumed that triggers would care for calling a programm
> at the right time (in the case of update-menus I would regard the
> rig
On Wed, 4 Jun 2008, Joey Hess wrote:
That would prevent update-menus from being run if a package was
installed not using apt.
Yes, this is correct. But what is actually the advantage of calling
update-menus using triggers instead of doing it in the postinst.
I always assumed that triggers wou
Andreas Tille wrote:
> in menu 2.1.39 the trigger feature was implemented. I wonder whether
> this implementation is really clever because update-menus which might
> take some time is called for every package that touches /usr/lib/menu
> or /usr/share/menu. While there is a migration path describ
Hi,
in menu 2.1.39 the trigger feature was implemented. I wonder whether
this implementation is really clever because update-menus which might
take some time is called for every package that touches /usr/lib/menu
or /usr/share/menu. While there is a migration path described in
#473467 which bri
11 matches
Mail list logo
