[AppStream] Requiring a specific version of something

[Joaquim Rocha]

Hey,

On Mon, Dec 19, 2016 at 7:47 PM, Richard Hughes <hughsient at gmail.com> wrote:

> On 19 December 2016 at 12:48, Matthias Klumpp <matthias at tenstral.net>
> wrote:
> > Can you be more specific about the first case? What exactly would be
> > the criterium for (not) showing the component?
> > (It's clear for the fwupd case, but not for the other one)
>
> From what I remember (jrocha, help!) it was that the "endless" plugin
> in gnome-software didn't know how to install the flatpak application
> in a way that it would appear on the front page of the Endless shell.


Yeah, this is something we had to create ad-hoc for us because e.g. Flatpak
introduced the extra-data functionality (pulling app contents on install
time) which is simply ignored in versions prior to 0.6.13.
So it'd be very convenient if we could hide an app
availability/"updatability" when a user has an older version.

I understand the logic about keeping away from a dependency hell, but it's
also something inevitable in any application story in the end, and we may
need to implement it if we want to provide the best experience for our
users.
I don't mind if we do it using simply metadata that GNOME Software consumes
and acts upon but making it an official spec would of course be better (so
projects outside of GNOME can also use it).

Joaquim Rocha  |  Endless
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/appstream/attachments/20161220/4f3d7f5f/attachment.html>