Flathub validations

[GeorgesStavracas]

Seems like Flathub requires quite a few undocumented extra validation steps:

• Run appstream-util validate from a relatively new appstream-glib (or via Flatpak from Flathub)
• The app-info directory in the build dir needs both app-info XML and 128x128 icons
• Screenshots need to be mirrored to https://dl.flathub.org/repo/screenshots (flatpak-builder: Add 'mirror-screenshots-url' input #63)
• Screenshots need to be committed to screenshots/$architecture (e.g. $ ostree commit --repo=repo --canonical-permissions --branch=screenshots/x86_64 builddir/screenshots)

I'm leaning towards either adding a flathub-validations boolean option to the flat-manager action, or adding a validations string array option. Not sure which one is better.

[bilelmoussaoui]

@GeorgesStavracas I would suggest adding a profile option to flat-manager that will automatically do everything needed for a flathub push. I don't think another profile will exist in the future and it will avoids us having a huge set of options to define and we avoid users not adding some validations to the list and publishing to the repo anyway

[razzeee]

Screenshots need to be mirrored to dl.flathub.org/repo/screenshots (flatpak-builder: Add 'mirror-screenshots-url' input flathub-infra/backend#63)

Can logos be mirrored too? See flathub-infra/website#49

[bilelmoussaoui]

Those apps do so for licensing reasons I believe.

[razzeee]

Not sure I get that, especially if you have a trademark, it shouldn't be problematic.

But we'll have problems with optimizing the pages, that show logos then, as we can't ensure, they're always there/loaded fast.