2015-09-05 3:49 GMT+02:00 Osamu Aoki <os...@debian.org>:

> [...]
> >    2. In addition to those changes, the Technical Committee resolves
> >       that packages providing a .desktop file shall not also provide a
> >       menu file for the same application.
>
> That's good idea in general.  I hope lintian warning should come soon.
>
> This reminds me some DE dependent .desktop file.  Is there any best
> practice how to do it for Debian?  KDE app not showing up on GNOME and
> vice versa.  How to decide how much .desktop data are NotShowIn for what
> environment?
>

In general: Do not use NotShowIn/OnlyShowIn for most applications.
There are only a few areas where it is actually useful, and this is almost
exclusively configuration tools specific to one desktop environment.


> Another question: Is there any list of DE names supporting .desktop
> file?  Whitelisting with "OnlyShowIn" entry requires such list.
>

You mean the list of registered desktop environments?
Take a look at
http://standards.freedesktop.org/menu-spec/menu-spec-latest.html#onlyshowin-registry



> Maybe we shoyld recommend explicit black list using "NotShowIn" entry
> over whitelisting with "OnlyShowIn" entry.
>

Why that? OnlyShowIn makes usually much more sense, but in general it
heavily depends on the case which of the keys makes the most sense.

Cheers,
    Matthias

-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/

Reply via email to