I usually get 'no-metainfo' warnings for Elementary OS applications. The metainfo file is ignored by appstream-generator, and just the desktop file is processed. Tested apps (on Arch Linux) with their metainfo files:
It seems that when I specify the corresponding desktop file explicitly in the metainfo file with the <launchable type="desktop-id"> tag, it solves the problem.
Elementary OS applications usually use the same name for desktop and metainfo files , e.g.:
I usually get 'no-metainfo' warnings for Elementary OS applications. The metainfo file is ignored by appstream-generator, and just the desktop file is processed. Tested apps (on Arch Linux) with their metainfo files:
It seems that when I specify the corresponding desktop file explicitly in the metainfo file with the
<launchable type="desktop-id">tag, it solves the problem.Elementary OS applications usually use the same name for desktop and metainfo files , e.g.:
/usr/share/applications/com.github.davidmhewitt.torrential.desktop/usr/share/metainfo/com.github.davidmhewitt.torrential.appdata.xmlSo could appstream-generator handle these applications better, or is the
<launchable>tag necessarily for the pairing?The text was updated successfully, but these errors were encountered: