2.0.9/2.1.0 test builds (do not merge yet)

[user1-github]

I opened this PR to test the latest 2.0.9 builds and see if something needs to be adjusted for the upcoming 2.1.0 release.

After 2.1.0 is released, we can update to it via this PR and merge it.

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

🚧 Started test build.

[flathubbot]

✅ Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/215092/net.redeclipse.RedEclipse.flatpakref

[user1-github]

@Calinou From the build log I noticed a new tessfont_linux binary is now being created. I remember I and AsciiWolf agreed to keep/ship all Red Eclipse binaries in the Flatpak, but I don't really understand what this new tessfont_linux binary does exactly. Is it going to be useful in the Flatpak?

Also, does RE support controllers or Steam Deck controls? I just noticed it has the --device=all permission, while almost all other shooters on Flathub have --device=dri.

[user1-github]

Otherwise, just tested this a bit, seems to work fine.

[AsciiWolf]

Also, does RE support controllers or Steam Deck controls? I just noticed it has the --device=all permission, while almost all other shooters on Flathub have --device=dri.

It's not only about Steam Deck controllers, but about gamepad support as a whole. And Red Eclipse should support gamepads - if I am not wrong, I actually tried this before enabling the all devices permission. The new --device=input permission is sadly still useless so this is the only way to get controllers working properly.

[user1-github]

The new --device=input permission is sadly still useless so this is the only way to get controllers working properly.

Interesting, I thought --device=input is useless only if you have versions of Flatpak older than 1.15.x. Maybe you need to use it in conjunction with --device=usb?

[AsciiWolf]

Well, I think that --device=input is still not supported on Flathub (or at least it wasn't when I last tried few months ago), but more importantly we also have to support older Flatpak versions that are still in use. (Flatpak 1.15.x is a development release that should not be used on stable systems and 1.16.0 was released in January this year - most distributions still use 1.14.x or older).

I am also not happy about the --device=all permission, but it is the best we have at the moment.

[user1-github]

Yeah, fair points.

[Calinou]

@Calinou From the build log I noticed a new tessfont_linux binary is now being created. I remember I and AsciiWolf agreed to keep/ship all Red Eclipse binaries in the Flatpak, but I don't really understand what this new tessfont_linux binary does exactly. Is it going to be useful in the Flatpak?

It's only useful for modders wishing to port fonts to the game, so you probably don't need to include it.

[Calinou]

Tested locally on Fedora 42, it works as expected.

[user1-github]

It's only useful for modders wishing to port fonts to the game, so you probably don't need to include it.

Yeah, it looks like it will also need filesystem access in order to be useful, so I leave it as is.

[AsciiWolf]

By the way, keep in mind that for the actual release, version information in AppStream metadata need to be updated too.

[user1-github]

Yes, I'm aware.

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

❌ Test build was cancelled.

[flathubbot]

🚧 Started test build.

[flathubbot]

✅ Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/217306/net.redeclipse.RedEclipse.flatpakref

[user1-github]

I've made some upstream metadata improvements which got accepted, so I'm bringing them here as well.

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

🚧 Started test build.

[flathubbot]

✅ Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/219408/net.redeclipse.RedEclipse.flatpakref

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

🚧 Started test build.

[flathubbot]

🚧 Test build enqueued.

[flathubbot]

❌ Test build was cancelled.

Help

• bot, build - Restart the test build
• bot, ping admins - Contact Flathub admins

[flathubbot]

🚧 Started test build.

[flathubbot]

✅ Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/232256/net.redeclipse.RedEclipse.flatpakref

Built for aarch64 and x86_64 architectures.

[AsciiWolf]

Looks good! Thanks again for your work on the Red Eclipse Flatpak. :-) We should probably move it to "Draft" though and switch it to "Ready" after the 2.1.0 gets released.

[user1-github]

Sure, you can turn the PR into a draft. Though it seems to me version 2.1.0 gets delayed quite a lot, so in case it won't be released before 26.08, I think we should just turn this into a runtime update PR and merge it because it also contains other improvements.

Regarding the last 2 commits from yesterday, I was just trying to see whether it's possible to use the upstream compile flags exclusively, without explicitly setting them in the manifest (because setting them in the manifest means we'll have to monitor the makefile for future changes in the primary flags). But the 2 options I tried don't work properly, so I opened another upstream PR to fix that in the makefile.