Loïc Minier <l...@dooz.org> writes: > (I have no idea why it's not mentionned anymore.) Yes, the program is > still used; it's in charge of generating > /usr/share/applications/mimeinfo.cache (and > /usr/local/share/applications/mimeinfo.cache); these files may then be > used by e.g. gio (in GLib) to map MIME types to .desktop files > (really applications). This can be used for example to open web > objects with the correct application according to its MIME type, or via > shared-mime-info + gio -- which allow mapping of a file's content or > filename to a MIME type -- to open any file with an application > handling this MIME type.
Thanks for the confirmation! > I can see how it would be useful to recommend calling dh_desktop as > soon as you distribute .desktop files just like it would be more useful > if we could inject any rules in packages via cdbs or the new "dh". > However, this is really packaging style and using an extensible > packaging style shouldn't be imposed by a checker tool like lintian; > I'm not aware of any different dh_desktop usage which would justify > raising a warning right now. > > Also, would we have to do more things on .desktop files, we would have > more options to implement them without requiring dh_desktop (triggers > come to mind). > > So not raising a lintian warning when dh_desktop isn't called on > .desktop file would be more to my taste. Okay, that matches my reasoning. I'll remove that tag in the next version of Lintian. Thank you very much! -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
