Bill Allombert <[EMAIL PROTECTED]> wrote: > On Thu, Sep 07, 2006 at 08:15:24PM +0200, Bill Allombert wrote: >> > What I would like from the debug option is information about menu files >> > that do not lead to creation of a menu entry, e.g. because the package >> > is not installed or there is an error in the file. >> >> Errors in the file are already reported. >> >> I will try to add a verbose output when files are discarded due to >> package check. Would that be sufficient ? > > Please try the attached patch that should do what you want.
Well, it does show the entries that are discarded because their package is missing. But it I think it does not solve the other problem I mentioned: JabRef doesn't get a menu entry, and I don't know why. I already manually checked that the package name was okay, because that's the only problem I was aware of. There are still cases where an entry is discarded, and I'd like to be able to find the reason for that. However, I'm not sure how important this is, since the problem only occurs with a backport on sarge (and with a recent menu package). I include below its menu file, mabye you can spot the error in it, and that may help to answer the question "So what else should it report about". But I think it would be best if it listed - all menu files considered (so we find out if the file placement or some naming convention is wrong) - all reasons not to create a menu entry for a given file I don't know how the creation of individual window managers' menus works, but if there's any chance of loosing an entry there, it should also pass an option to the menu-methods (?) script for each window manager, and these scripts should handle this option properly (which then is a task for the window manager's maintainer, I guess). So here's the menu file: ?package(jabref):needs="x11" \ section="Apps/Tools" \ title="JabRef" \ command="jabref" \ icon="/usr/share/pixmaps/jabref32.xpm" \ icon32x32="/usr/share/pixmaps/jabref32.xpm" \ icon16x16="/usr/share/pixmaps/jabref16.xpm" As I said, in a sid chroot this ends up in fluxbox' menu file, while on sarge with menu_2.1.30 it is missing in fluxbox' and WMaker's menu file. Regards, Frank P.S. I've recently filed a bug against jabref, demanding that it be moved from Apps/Tools to Data managment. This has been fixed, but at the same time a lintian override has been added: jabref binary: menu-item-creates-new-section but I have not found a bug in lintian requesting to allow new sections. Are these new names still experimental? -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
