I packaged the game as a flatpak

[Wildeblood]

So it looks for an AddOns dir next to the .app dir?

Yes.

[sharpenedblade]

Can pr#515 be merged soon, the last blocker for the flathub package is the appstream metadata. Once the metadata is upstream the pr can be tested according to the flathub merge process.

[another_commander]

I haven't merged it because I have no say on the Linux builds nor way to confirm the functionality of the PR. Would appreciate one of the Linux guys with access to the project on github making the decision to press the merge button, provided they are good with the contents of the PR.

[MrFlibble]

#515 looks mostly good to me.

Does the 'requires' section need 'display length', and if so, should the (presumably minimum) be as high as 768.

[sharpenedblade]

I haven't merged it because I have no say on the Linux builds nor way to confirm the functionality of the PR

#515 is just metadata for gui software apps, the actual build artifact is in #516.

Does the 'requires' section need 'display length', and if so, should the (presumably minimum) be as high as 768.

768 is what the flatpak docs say to use for desktop only apps. Flatpak doesn't strictly enforce the display length tag so desktops/laptops with smaller screens will still work. The tag actually means that it should not show up as a mobile app. https://docs.flathub.org/docs/for-app-a ... -only-apps

[MrFlibble]

I haven't merged it because I have no say on the Linux builds nor way to confirm the functionality of the PR

#515 is just metadata for gui software apps, the actual build artifact is in #516.

Does the 'requires' section need 'display length', and if so, should the (presumably minimum) be as high as 768.

768 is what the flatpak docs say to use for desktop only apps. Flatpak doesn't strictly enforce the display length tag so desktops/laptops with smaller screens will still work. The tag actually means that it should not show up as a mobile app. https://docs.flathub.org/docs/for-app-a ... -only-apps

Thanks for the clarification.

Do mobile devices need excluding? Surely a mobile device/tablet with e.g. a Bluetooth keyboard would be fine.

[sharpenedblade]

Do mobile devices need excluding? Surely a mobile device/tablet with e.g. a Bluetooth keyboard would be fine.

The examples in the flathub docs add touch support for all mobile/tablet apps. Mobile flatpak can still install "desktop" apps, they just are not in the mobile section of flathub (edit: actually it will just give you a warning about compatibility, then install it like normal), so if someone does have a keyboard and wants to install the flatpak they still can.

[MrFlibble]

Do mobile devices need excluding? Surely a mobile device/tablet with e.g. a Bluetooth keyboard would be fine.

The examples in the flathub docs add touch support for all mobile/tablet apps. Mobile flatpak can still install "desktop" apps, they just are not in the mobile section of flathub (edit: actually it will just give you a warning about compatibility, then install it like normal), so if someone does have a keyboard and wants to install the flatpak they still can.

Sweet!

[hiran]

I haven't merged it because I have no say on the Linux builds nor way to confirm the functionality of the PR. Would appreciate one of the Linux guys with access to the project on github making the decision to press the merge button, provided they are good with the contents of the PR.

Difficult to tell what it does. It adds another build job to the workflow that seems completely independend from everything that is in place already. So I'm wondering how the version calculation would be done, or how the up to date documentation goes in there.

Also there is no build artifact to be inspected.