<div dir="ltr">On Tue, Dec 12, 2017 at 12:05 PM, Matthias Klumpp <span dir="ltr"><<a href="mailto:matthias@tenstral.net" target="_blank">matthias@tenstral.net</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">2017-12-12 9:33 GMT+01:00 Alexander Larsson <<a href="mailto:alexl@redhat.com">alexl@redhat.com</a>>:<br>
> What exactly does this mean:<br>
><br>
> ```<br>
> <component type="desktop-application"><br>
> <id>org.example.FooBar</id><br>
> <launchable type="desktop-id">foobar.<wbr>desktop</launchable><br>
> <provides><br>
> <id>foobar.desktop</id><br>
> </provides><br>
> ...<br>
> </component><br>
> ```<br>
><br>
> Suppose the upstream app has a foobar.desktop file (with corresponding<br>
> id=foobar.desktop in the appdata file).<br>
<br>
</span>That's not necessary (anymore) and not even wanted, because the ID can<br>
be independent from the .desktop filename of the application, and<br>
should (sometimes must) follow a reverse-DNS scheme.<br>
<span class=""></span></blockquote><div><br></div><div><br></div><div>But we don't want to go back to the bad old days of multiple ids per application (desktop file name, appstream id, flatpak id, dbus name...) - we chose to unify them for a reason. <br></div></div></div></div>