[AppStream] New component types

[Matthias Klumpp]

2016-07-19 14:14 GMT+02:00 Richard Hughes <hughsient at gmail.com>:
> On 19 July 2016 at 12:56, Matthias Klumpp <matthias at tenstral.net> wrote:
>> In order to allow non-GUI apps to get their own component type, in
>> order to easily filter them out, I would like to have a few more
>> component types, and deprecate the "desktop" type along the way.
>
> Being honest, I think that would further confuse application upstream
> maintainers. They're already confused from the <applications> ->
> <component> and appdata->metainfo changes. At some point you have to
> decide if removing the old way of doing things is worth the pain of
> migration, and I really don't think there is nearly enough
> justification for renaming the desktop group.

It won't be advertised and I won't push people to change the value (=
no validator message about this).
This would be a change to harmonize the spec, and to probably have a
component which actually describes a desktop environment in some
distant future.

>> console
>
> I think just console is fine. If it's really a console (e.g. bash) I'm
> skeptical why it needs a metainfo file at all.

It needs a metainfo file to get a unique AppStream ID, make its CVE-ID
known to the system and to show up in Snappy stores etc. Argueably, I
would want to this to be a generic component, no need to add a
separate component type for a tiny group of tools.
For just "console": That name is imprecise, and I really dislike these
imprecisions... "console-app" or "cli-app" is more precise.

Cheers,
    Matthias