[AppStream] Requiring a specific version of something

[Richard Hughes]

On 20 December 2016 at 09:56, Matthias Klumpp <matthias at tenstral.net> wrote:
> just like it uses
> Flatpak to determine the size of the download and whether the bundle
> is installed at all.

I guess it could go in the flatpak metadata.

> For that I would rather like to see a new <price/> tag (with
> upstream's suggestion on how much this should cost), and the backend
> (PackageKit/Flatpak/whatever) should determine whether a Payment is
> necessary or optional.

Okay, that probably makes sense and we can discuss the metadata format
for payment stuff when we actually get some details.

> At time, I do like AppStreams rather small scope, because it gives the
> project focus and clearly defines what it is

Right, and that's not insane; I think working together we can build
something that's maintainable in the long term.

>> <value key="BootloaderVersion" type="version-least">0.1.0</value>
> Add extra tag requires_bootload

Lets concentrate on this for now. I'm not sure putting the bootloader
name in the tag; there can actually be multiple layers of firmware (up
to 4!) each with slightly different semantics and names for each
device.

What about:

<require_version id="bootloader" compare="version-least">0.1.0</require_version>
<require_version id="firmware" compare="version-most">0.5.1</require_version>
<require_version id="validation" compare="exact">17</require_version>

Open to ideas.

Richard.