On Fri, Jun 20, 2014 at 10:27 PM, Moritz Mühlenhoff <j...@inutil.org> wrote: > On Wed, May 14, 2014 at 10:54:33AM +0200, Julian Andres Klode wrote: >> Package: elinks >> Severity: minor >> >> elinks is a console application. Console applications should not >> ship .desktop files. Those are for graphical applications only. > > Do you have a reference for that?
It's not specified anywhere AFAIK, but see the arguments below. > > The desktop file has been around for a long time and there are a > lot of other terminal-based apps using one. I have not seen any other app. Major apps like aptitude don't, mutt ships one with NoDisplay=true as it only registers a mime handler. Lynx does not ship any desktop file. IPython ships a desktop file, but this is a bit special, since that's an interactive shell. For a terminal-based web browser, it does not make much sense, though, as you'll likely have a graphical browser installed if you run a desktop environment. Most likely the user installed elinks as a fallback for the terminal, or for dumping HTML, potentially for use with mutt. It might make sense to still ship the desktop entry with NoDisplay=true, so advanced users can still enable it if they need it. But it does not make sense IMO to clutter up the default menu with a console application most do not need there. This is worse now as it was previously, with (for example) GNOME 3 now only giving a grid of applications, no categories anymore. Imagine how filled it would be if every terminal app shipped a desktop. IIRC, one of the major reasons the Debian menu was disabled in GNOME was to avoid all the console applications being displayed. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
