[AppStream] Dependencies on things in AppStream

[Richard Hughes]

On 26 March 2018 at 19:12, Matthias Klumpp <matthias at tenstral.net> wrote:
> The reason for using MB would be that I think for smaller systems it
> would make sense to define "needs 1.5GB of space" (like phones, for
> example), and that I would like to use the same unit size for the
> "needs at least X amount of free space"[1] requirement, where MB would
> make sense too, I think.

For the phones case I can see Mb being a better unit, sure.

> I haven't looked at what appstream-glib does, but at the moment in my
> mind I imagine a single AsDependency class with types similar to
> Asprovided and an importance property of REQUIRED or RECOMMENDED.

Is as a dependency? Dependencies are a two way thing, with all the
legacy stuff people thinks of as a "dep" -- in as-glib I went for
AsRequire -- i.e. things the component requires.

> Is this some kind of workaround for weird firmware vendors?

Yes and yes.

Richard.