Closed probonopd closed 1 year ago
Recent versions of AppStream validation tools now want to enforce that you use something like org.appimage.appimagetool.desktop instead of appimagetool.desktop, even though the former is way simpler and works perfectly fine for our use case.
They always have, as far as I can tell. And this is only a problem when you specify appstream data at all. So this should not be the one use case on which you build your case...
In general, if there is AppStream data, it should be valid. I don't think ignoring errors is a good idea, though. We can ignore warnings safely in my opinion, but for errors...
How about adding some CLI parameter or environment variable to disable the check?
Right, -n, --no-appstream Do not check AppStream metadata
. Maybe that's all that's needed.
Recent versions of AppStream validation tools now want to enforce that you use something like
org.appimage.appimagetool.desktop
instead ofappimagetool.desktop
, even though the former is way simpler and works perfectly fine for our use case.Since AppStream validation tools are constantly changing and with them the rules are a moving target, it's almost impossible to support AppStream for the long run without constantly fiddling around.
As a result, we might consider to make AppStream validation errors just non-fatal warnings.