New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
appstream-builder creates files with invalid component type "shell-extension" #260
Comments
Libappstream needs to not fail if it encounters unknown types or tags. |
I don't care who fixes this issue. |
"be conservative in what you do, be liberal in what you accept from others." -- it's XML, the X stands for extensible. We can't lock the specification and make no changes, and neither can we go back in time and make different design decisions. Sorry, but I don't think there's much I can do. Long term we can migrate to the addon thing, but that's going to need the clients being changed as well. |
It doesn't fail, it just warns about it. Libappstream will never ignore components and not give the user/developer any hint on why it was dropped or that something was ignored. |
By that logic, appstream-builder should stop to produce wrong component types.
The only client using this is AFAIK GNOME Software. To migrate long-term I would leave the bug open, so it doesn't get forgotten. |
@ximion - shouldn't his be ximion/appstream#199 , which you closed btw? |
@StefanBruens No, that one is closed because it will never be changed. The |
shell-extension is no valid component type, the correct type for GNOME shell extensions would be "addon".
This breaks loading of metadata with e.g. appstreamcli, or any of the appstream bindings, e.g. AppstreamQt.
See ximion/appstream#199 for more info.
The text was updated successfully, but these errors were encountered: