.desktop file to be visible in application menus.
.desktop files to represent an application in the AppStream metadata pool. Upstream projects should ship a small XML file containing additional metadata to describe their application though, to enhance the available metadata. This data includes things like screenshots, long descriptions, icon information and various other things needed to present the application properly to the user. For some distributions, the presence of this metadata is a prerequisite for the application showing up in the metadata pool and being presented in software centers.
.desktop file. Applications can ship one or more files in /usr/share/metainfo/%{id}.appdata.xml.
Note
type property set to desktop, while in a generic component this property can be omitted. This clearly identifies this metainfo document as describing an application.
Note
<id/> tag value must be the same name as the installed .desktop file for the application, the .desktop suffix of the filename may be omitted.
.desktop files follow the reverse-DNS scheme name already. If they do not follow the scheme, it is strongly recommended to change the .desktop filename. Refer to the desktop entry specification for more information.
.desktop file is named org.example.FooBar.desktop the component-id must be org.example.FooBar (or org.example.FooBar.desktop). If your application's .desktop file is named frobnicator.desktop the component-id must be frobnicator (or frobnicator.desktop) - it is highly recommended to modernize the .desktop filename to follow the Desktop Entry specification in these cases though.
<metadata_license/> tag as described in <metadata_license/> must be present.
Name field of the .desktop file. In some cases it might be required to have a different name in the software center, but most metainfo files will not need this.
name tag and no Name field is present, the metadata is considered invalid and might be ignored by the AppStream generator.
desktop-application metainfo file it is only essential if the accompanying .desktop file does not have a Comment= field. If the metainfo file has a summary, it wil override the value found in the Comment field of the .desktop file.
summary tag and no Comment field is present, the metadata is considered invalid and might be ignored by the AppStream generator.
<screenshots/> tag should look like it is described at <screenshots/>.
PATH, you should add at least a child of type <binary/> to make that new executable known to the distribution.
<releases/> tag, which has one or more <release/> childs to define the version and release date of this application. For details, see <releases/> .
desktop-application, the following tags are required and must always be present: <id/>, <description/>, <metadata_license/>. The following tags are strongly recommended / required conditionally: <name/>, <summary/>.