-
Notifications
You must be signed in to change notification settings - Fork 44
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
Fix appdata.xml #128
Fix appdata.xml #128
Conversation
Also, consider adding an actual screenshot instead of https://raw.githubusercontent.com/dave-theunsub/clamtk/master/images/clamtk_300x300.png. :-) You can probably use one from Flathub. |
Fix incorrect app id and add correct component type
@dave-theunsub Feel free to let me know if there is any problem with this PR. :-) |
Sorry I'm moving slow - I'll get to it. :) |
Hi @AsciiWolf , I'm getting error messages with your inputs:
So I used this page for reference: https://freedesktop.org/software/appstream/docs/chap-Quickstart.html https://gist.github.com/dave-theunsub/68faf2078253e5f832bd0e1df04c3b3d Returns this: What do you think? |
Hi Dave, yeah, I have noticed this too. It is not caused by my PR. The appstreamcli validator does not like the local icon that is specified in this AppData file. But the AppStream standard itself allows local icon types, so it should be fine. I think that most AppStream parsers will ignore this tag if they do not support it. Ideally, there should not be this tag in the AppData file (it should not be needed if you specify a correct id matching the desktop file name in AppData - which is what exactly my PR does) and icons should be installed in /usr/share/icons/hicolor/*/apps/ since /usr/share/pixmaps/ is a legacy icon location, but I think (however I am not sure) that this legacy location is now also supported by most parsers/generators. Anyway, I would keep this tag in the AppData file, it hopefully should not do any harm and is probably good for legacy reasons (for older AppStream parsers that do not support the legacy icon location). You can safely remove this tag if you change the default desktop icon installation directory to |
By the way, the gist you linked is also incorrect: https://gist.github.com/dave-theunsub/68faf2078253e5f832bd0e1df04c3b3d#file-clamtk-appdata-xml-L4 - You fixed the id to be a correct rDNS one, but 1. the appdata file should have the same (com.github.davetheunsub.clamtk.appdata.xml) name as rDNS id; 2. the desktop file should also have the same name or you can add |
Any update? |
Still working it, thanks. |
Please, let me know if there is anything (regarding the AppData) I could help with. Thanks! |
Ok, in one post, let's put together everything that needs to be done. Can you put the entire file contents in one gist? And with what you wrote in #128 (comment) and #128 (comment)? I think those two parts confused me slightly. Thanks for the help. |
Hi Dave, as I said, there are two different approaches to fix the issue:
|
There is other small thing that I mentioned before: You are installing a desktop icon to a legacy |
Ok, it's merged. I would like to keep the legacy path for now and change later. One thing left to do: fix |
That warning is about the desktop id not being rDNS. That is what I talked about in the first point of my previous comment. It is just a warning and should not be a problem. If you would like to fix it, you would need to do all the things mentioned in the second point. But I also think that the legacy path should be good for now. Thanks! |
Fix incorrect app id (and add correct component type) that is not correct rDNS and does not match desktop file name, see: https://bugzilla.redhat.com/show_bug.cgi?id=1819344#c6
@dave-theunsub Feel free to review and merge. :-)