On April 25, 2004 15:26, Chris Cheney wrote: > The part of kde that reads the menu is actually in kdelibs-bin > "/usr/bin/kde-menu" which is used by various apps that ask you what to > open something with. So at the very least kdelibs-bin would also have > to have the suggests along with possibly kicker... That was the reason > the menu's were first moved to kdelibs-bin before being split out into > their own separate package.
Ah, I see. From the point of view of the packager or developer, menu-xdg enhances kdelibs-bin, because menu-xdg relates to /usr/bin/kde-menu, which is provided by kdelibs-bin. But from the point of view of the end user, kicker provides the K menu, and it is noticeably altered by menu-xdg. Thus it should Suggest menu-xdg as well. According to this rationale, kdelibs should document the details of how it all works and why a separate package (menu-xdg) is now needed. Kicker should explain to the end-user what the Suggest will do for them, either in the package description or a README.Debian (or both). Cheers, Chris
