Hello Joey,
On Sun, Mar 30, 2008 at 04:06:15PM -0400, Joey Hess wrote:
- Adding a debian/triggers file (which is installed by debhelper),
and which registers interest in /usr/share/menu and /usr/lib/menu.
This causes dpkg to trigger menu whenever files in those directories
are changed.
Bill Allombert wrote:
Hello Joey,
On Sun, Mar 30, 2008 at 04:06:15PM -0400, Joey Hess wrote:
- Adding a debian/triggers file (which is installed by debhelper),
and which registers interest in /usr/share/menu and /usr/lib/menu.
This causes dpkg to trigger menu whenever files in those
Bill Allombert wrote:
I didn't add trigger support for menu-methods files. It would probably
be possible to add that, but since there are not a lot of them, it
didn't seem worthwhile at this point. Packages with menu-methods can run
update-menus as usual.
What would be the cost to add
On Sun, Mar 30, 2008 at 04:06:15PM -0400, Joey Hess wrote:
The attached patch makes menu support triggers, as implemented in dpkg
in (currently) experimental.
Hello Joey,
Thanks a lot for your patch and analysis.
My comments:
- Adding a --real option to update-menus. This can be used to
Hi!
+case $1 in
+triggered)
+ # This is triggered by any installation of a menu file and by
+ # any call to update-menus made in a package maintainer script.
+ update-menus --real
+;;
+*)
Joey, I was wondering if there should be an exit 0 after processing
the trigger.
Michael Biebl wrote:
Hi!
+case $1 in
+triggered)
+ # This is triggered by any installation of a menu file and by
+ # any call to update-menus made in a package maintainer script.
+ update-menus --real
+;;
+*)
Joey, I was wondering if there should be an exit 0
Package: menu
Version: 2.1.39
Severity: normal
Tags: patch
The attached patch makes menu support triggers, as implemented in dpkg
in (currently) experimental.
When used with an older version of dpkg, menu's current behavior is
unchanged, so there's no transition issue. This patch can be applied
7 matches
Mail list logo