Package: menu
Version: 2.1.39
Severity: normal
Hi,
when bug #484167 was filed against cdd-common package I wondered how to
prevent the problem reasonably. So I inspected menu.postinst and found the
snippet
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 --trigger
exit 0
and I wondered whether I could easily detect whether cdd-menu was
called in a trigger process and some extra options / environment
variables were set to be able to detect that a trigger was caused.
Unfortunately the option --trigger is not documented in
man update-menus
Please provide some information about the effect of this command line.
Kind regards and thanks for maintaining menu
Andreas.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages menu depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libgcc1 1:4.3.0-5 GCC support library
ii libstdc++6 4.3.0-5 The GNU Standard C++ Library v3
menu recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
