On 2010-08-10 08:04, Michelle Konzack wrote:
Am 2010-08-10 01:25:11, schrieb Filipus Klutiero:
Package: menu
Version: 2.1.43
Severity: normal

When menu is removed, it leaves generated menu files behind.
IF "menu" is removed, you will have an non-usable X-Window-System.
No, I'm currently on X and menu is not installed.
At least here, because there are more  then  20  programs  including  my
Window-Manager which depend on it.

And removing autogenerated menu.hook files would lead  to  the  hell  of
errors for some WindowManagers, which mean, removing is NO solution.

THE IMPORTANT QUESTION IS:
   How do you have removed "menu" without removing the half workstation?
I just removed menu. Nothing else was uninstalled.
Some programs which depend on menu:

----[ comman 'apt-cache rdepends menu |tr -d ' ' |sort' ]---------------
apt-file
cdd-common
debconf
doc-linux-html
doc-linux-nonfree-html
fvwm
keytouch-editor
linpopup
openoffice.org
pdmenu
startupmanager
synaptic
tdfvwm-menu-common
w3m
w3mmee
wmanager
xmahjongg
xvt
debconf doesn't depends on menu, it just conflicts with some menu version. I suppose most others are wrong.
These
files then stop being maintained. Consequently, if a package
providing a menu item when menu was last installed is removed after
menu is removed, the generated menu item remains in the menu
hierarchy. At least in KDE, this means the menu item keeps being
displayed in the Debian menu (when menu-xdg is installed). For
example, if smb4k, menu-xdg and menu are all installed, if menu is
removed then smb4k is removed, the menu item "SAMBA for KDE" remains
in the Debian menu. If a user tries to launch smb4k, it obviously
fails, without any feedback.
Better you tell the maintainer of "smb4k",  that  it  should  depend  on
"menu" :-D, because otherwise menu.hook files are not updated accordenly
smb4k doesn't depend on menu. It provides a menu file, but it works fine if the file is not used. The menu files not being updated is a systemic problem which should be fixed globally.



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to