Re: AppStream issues with various KDE applications
- Date: Fri, 6 Jan 2017 20:26:37 +0100
- From: Matthias Klumpp <matthias@xxxxxxxxxxxx>
- Subject: Re: AppStream issues with various KDE applications
2017-01-04 21:43 GMT+01:00 Richard Hughes <hughsient@xxxxxxxxx>:
> On 4 January 2017 at 16:55, Matthias Klumpp <matthias@xxxxxxxxxxxx> wrote:
>> @hughsie: I am wondering for some time now whether we should make the name
>> and summary tags essential for desktop-application type components in
>> metainfo files as well.
> For appstream-glib, it is.
Oh, really? Because the spec says the name/summary is taken from the
.desktop file if the metainfo doesn't contain it, which IMHO was a bad
idea (while reducing the amount of metadata one needed to write, it
also made metainfo files less useful because they were not
So, if appstream-glib already enforces name/summary to be present in
metainfo files, I'd be more than happy to do the same for AppStream
itself and change the specification accordingly.
>>This would make validation a bit more failsafe and
>> result in more complete metainfo files. I might raise this at the AppStream
>> ML for comments this week...
> I'd support this proposal :)
By the way, I looked at Debian/Ubuntu/Neon/Arch which are using the
appstream-generator, and most of the issues you mention didn't appear
there because apparently Fedora's KDE software versions are pretty
old. The ones that did appear were caught by our CI systems already,
so just nobody cared for fixing them yet...
In any case, given the huge amount of metainfo files we have in KDE,
the number of broken ones is pretty small. Still, fixing yellow CI
statuses is important...
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/