Appstream ID and Flatpak

Matthias Clasen mclasen at redhat.com
Wed Dec 13 18:06:06 UTC 2017


On Tue, Dec 12, 2017 at 12:05 PM, Matthias Klumpp <matthias at tenstral.net>
wrote:

> 2017-12-12 9:33 GMT+01:00 Alexander Larsson <alexl at redhat.com>:
> > What exactly does this mean:
> >
> > ```
> > <component type="desktop-application">
> >   <id>org.example.FooBar</id>
> >   <launchable type="desktop-id">foobar.desktop</launchable>
> >   <provides>
> >     <id>foobar.desktop</id>
> >   </provides>
> >   ...
> > </component>
> > ```
> >
> > Suppose the upstream app has a foobar.desktop file (with corresponding
> > id=foobar.desktop in the appdata file).
>
> That's not necessary (anymore) and not even wanted, because the ID can
> be independent from the .desktop filename of the application, and
> should (sometimes must) follow a reverse-DNS scheme.
>


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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/flatpak/attachments/20171213/15018b9c/attachment.html>


More information about the Flatpak mailing list