Matthias Klumpp

@mariobl LGPL is no permissive license, so this change will be rejected as well. You will want something like the FSFAP license. AppStream will currently only recognize those licenses as...

@nbraud Could you maybe just ask upstream for clarification? We can't accept copyleft licenses in metainfo because the data contained in them gets aggregated into one big file, which would...

What do you mean with "isn't visible"? Does libappstream not read it when it's present (it should), or is the `custom` entry not present in the source XML? In the...

What do you expect the specification to say about it? Looks like you kind of already found the source of your issue, with a solution for it. The `custom` tag...

> [...] > > If this release metadata file is split out from the main MetaInfo file, the MetaInfo file can contain an empty releases block, containing an URL that...

So, with regards to fwupd, that uses JCAT https://github.com/hughsie/libjcat for all its signing needs, to support multiple signatures on multiple files.

@pwithnall > Please keep the release entry for the most recent release of each component in the collection XML, as per my previous comment. Otherwise gnome-software will end up downloading...

Since this is on the list of essential things for AppStream 1.0, I am thinking about implementing this feature by: * Not adding extra metainfo signing * Enforcing HTTPS for...

Thank you for the patch! I do think `requiresComponents` is a terrible name though, because pretty much anything can be required, including screen dimensions, memory, mime-handlers or binaries, and not...

> > In C++20 requires is a reserved keyword > > That kind of change seems somewhat, well, hostile to your existing userbase... Yeah, it *really* sucks, it basically forces...