Hi,
I'm having a hard time double-guessing how my package's .appdata.xml is processed at the distro level (I presume, by appstream-builder).
I validated it with fedpkg already, but there are lots of undetected issues, such as restricted icon search path, same-package constraints, etc.
Is there a log of how the AppStream Collection Metadata for Fedora is generated, so I can look for errors? (alternatively is there an easy way to pre-test this locally?)
Cheers! Sylvain
I found some minimal status at: https://dl.fedoraproject.org/pub/alt/screenshots/f30/matrix.html also it doesn't seem updated often (last update 2 weeks ago).
Is there anything else?
- Sylvain
On 29/01/2019 10:35, Beuc wrote:
Hi,
I'm having a hard time double-guessing how my package's .appdata.xml is processed at the distro level (I presume, by appstream-builder).
I validated it with fedpkg already, but there are lots of undetected issues, such as restricted icon search path, same-package constraints, etc.
Is there a log of how the AppStream Collection Metadata for Fedora is generated, so I can look for errors? (alternatively is there an easy way to pre-test this locally?)
Cheers! Sylvain _______________________________________________ Fedora Games SIG mailing list -- games@lists.fedoraproject.org To unsubscribe send an email to games-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/games@lists.fedoraproject.org