For some reason that confuses me a bit. The first line after the example says "we're going to talk about --vendor in the context of the menu spec", then the first item says not to use --vendor at all and the second item talks about KDE and --dir.
Plus, I'm not sure how I'm supposed to know if the upstream provides vendor_id.
How about three examples:
Proposed desktop-file-install examples:
If upstream provides a desktop file, does it include "Vendor:" (or however I'm supposed to know that it specifies vendor_id:)? If so, use this:
[[ blah ]]
KDE applications not falling into the above category should use the following: (or put this first if KDE-ness overrides the other options)
[[ blah ]]
Otherwise, use the following:
[[ blah ]]
Jason L Tibbitts III wrote:
For some reason that confuses me a bit. The first line after the example says "we're going to talk about --vendor in the context of the menu spec", then the first item says not to use --vendor at all and the second item talks about KDE and --dir.
In the context of --vendor, using a subdir is (relatively) equivalent.
Plus, I'm not sure how I'm supposed to know if the upstream provides vendor_id.
If the .desktop filenames are either of the form: vendor/foo.desktop or vendor-foo.desktop then upstream is providing them.
Does that help?
-- Rex
Jason L Tibbitts III wrote:
For some reason that confuses me a bit. The first line after the example says "we're going to talk about --vendor in the context of the menu spec", then the first item says not to use --vendor at all and the second item talks about KDE and --dir.
Plus, I'm not sure how I'm supposed to know if the upstream provides vendor_id.
OK, I updated the draft to include 2 examples, one using --vendor=<vendor_id> the other using --dir=%buildroot%_datadir/applications/<vendor_id> --vendor=""
and included language from the spec describing the difference (hopefully):
------------------- To prevent that a desktop entry from one party inadvertently cancels out the desktop entry from another party because both happen to get the same desktop-file id it is recommended that providers of desktop-files ensure that all desktop-file ids start with a vendor prefix... Please namespace the filename, as in "vendor-foo.desktop", or use a subdirectory of datadir/applications/ so you have "vendor/foo.desktop"... -----------------
-- Rex
On Tuesday 26 September 2006 17:51, Rex Dieter wrote:
See http://fedoraproject.org/wiki/PackagingDrafts/DesktopFiles
Comments?
It's not about desktop-file-install but about the desktop-file itself: I propose to provide some guidelines about the contents of a desktop-file, e.g. that they should not contain paths in the Exec entry and should provide a StartupWMClass entry. Another issue is, which / how many Categories should be added, every categores that fits like for example "Application;AudioVideo;Audio;Midi;Music;" for an midi application that generates midis or only some of them?
Regards, Till
Till Maas wrote:
It's not about desktop-file-install
Well, *this* proposal is limited in scope only to the use of desktop-file-install.
but about the desktop-file itself:
I propose to provide some guidelines about the contents of a desktop-file, e.g. that they should not contain paths in the Exec entry and should provide a StartupWMClass entry. Another issue is, which / how many Categories should be added, every categores that fits like for example "Application;AudioVideo;Audio;Midi;Music;" for an midi application that generates midis or only some of them?
Agreed, some extra guidelines should be written to cover these topics as well. Are you volunteering? (:
-- Rex
packaging@lists.fedoraproject.org
-
Jason L Tibbitts III -
Rex Dieter -
Till Maas