Matthias Klumpp

Something like this may actually also help with issues like https://github.com/ximion/appstream/issues/365 (at least if used for Flatpak stuff)

Release artifacts already have a "platform" component, maybe having something like this for screenshots makes sense... With localized screenshots, theme-specific screenshots and all the other stuff people want to specialize...

Having an `icon-theme` component type is on my radar, for that kind of component it's relatively easy to define since this one has an XDG specification. Component-types should never be...

I'll add an `icon-theme` component with a future (next or the one after) release, but for GTK+ and other themes I think it's best if they are addons. Maybe in...

I would expect - going with the current idea - that a package like `arc-theme` would contain multiple metainfo files, one for each part of the theme, but with the...

> > would contain multiple metainfo files > > Ah, this was the missing piece of information - I hadn't realised that was possible/allowed. It's perfectly fine :-) However, ideally...

AppStream has `icon-theme` now, available with the next release (to be released today). I think autogenerating the icon-theme metadata from theme index files is probably not a great idea, so...

@hughsie I have no objections to allowing ISC as well - do you see any issues allowing it would cause for you / Red Hat / Fedora?

@hughsie I agree in principle, and I *really* don't want to add more licenses. Personally I think just having `FSFAP` should satisfy all requirements. With ISC being so close to...

> When was MIT, 0BSD and FTL added? Why were they added? Since AppStream existed, as originally it was allowing all permissive licenses. So at first, I just compiled a...