Skip to content
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

Permission to Publish to Flathub #22

Closed
keplersj opened this issue Mar 15, 2022 · 14 comments
Closed

Permission to Publish to Flathub #22

keplersj opened this issue Mar 15, 2022 · 14 comments

Comments

@keplersj
Copy link

Hi @jorio!

Thank you for porting this to modern operating systems and bundling an AppImage for Linux. I have created a Flatpak package for this project, ready to publish to Flathub. With your permission I would like to publish the Flatpak I've created to Flathub to allow even broader access to this classic (including on the recently released Steam Deck).

Please let me know if there are any questions I can answer, thanks!

@jorio
Copy link
Owner

jorio commented Mar 15, 2022

Hi @keplersj! Great initiative! As long as the build process can be audited, that's fine by me. It looks like everything happens in the open with Flatpak packages so it's all good.

Contrary to what BUILD.md currently says, I recommend using CMAKE_BUILD_TYPE "RelWithDebInfo" rather than "Release" because it might come in handy in case of crashes. I don't know Flatpak's policy regarding shipping debug symbols, though.

Also, for what it's worth, I have a series of bugfixes in the pipeline for Bugdom, and I intend to make a maintenance release probably next month. Do you plan to maintain the Flatpak package when updates come out?

@keplersj
Copy link
Author

keplersj commented Mar 15, 2022

Yes! Flathub's build pipeline is very robust and transparent. I believe Flathub tries to avoid shipping debug symbols, but it is possible to build and run a version of the application with debug symbols with Flatpak very easily if needed.

Updating the Flatpak is pretty easy and I was planning to take the lead on it (and looking to use an automated tool to automate the update process: flatpak-external-data-checker). The manifest just pulls a Git ref from this repo and builds it for x86_64 and aarch64.

While I have you, can I have your permission to publish the other Pangea games you've ported to Flathub?

Thanks! I really appreciate all the work you've put into these games. It makes me very happy to see these games from the iMac I grew up on given such great attention.

@jorio
Copy link
Owner

jorio commented Mar 15, 2022

Yes, please do the other Pangea games!

FYI, an update for Mighty Mike is right around the corner as well. It currently lacks a lot of the CI/packaging stuff that's in the other games, but you can use package name "io.jor.mightymike" for it.

I'm glad you're enjoying the games :) I also grew up with them and it's been lots of fun to get them up and running again!

By the way, now that you've mentioned the Steam Deck, I'm curious about how Bugdom fares on it. The menus and the pause screen currently require a mouse; does the Deck's touchscreen work well in those? If that's a problem, I can look into making the menus controller-friendly.

@keplersj
Copy link
Author

Truthfully I'm not sure, I don't have a Deck just know Valve made Flatpak a first-class citizen in the immutable Arch it's preloaded with. If Deck touchscreen works anything like the touchscreen on the tablet (1st Gen Surface Go running Arch) I wrote the manifest on, the menus were decently touch friendly.

@keplersj
Copy link
Author

Also, thought I'd share that the aarch64 build of Bugdom works pretty well on postmarketOS running Flatpak:
20220315_15h49m12s_grim
20220315_15h49m56s_grim
20220315_15h50m12s_grim
20220315_15h50m36s_grim

@jorio
Copy link
Owner

jorio commented Mar 15, 2022

Cool! Thanks for sharing!

Can we try to get rid of the pixelation? If you have time, I wonder if adding SDL_WINDOW_ALLOW_HIGHDPI to the flags passed to SDL_CreateWindow in Main.cpp makes a difference.

@keplersj
Copy link
Author

Of course! Here are screenshots from a build with the following patch applied (070381a):
20220315_17h03m04s_grim
20220315_17h03m19s_grim

@juxuanu
Copy link

juxuanu commented Mar 16, 2022

@keplersj Thanks for the Flatpak. Any indications of how can I port my saved games there? I used to compile it myself with the PKGBUILD in the AUR, but the Flatpak is much more convenient. I allowed access to ~/.config/Bugdom but it did not detect them.

Thanks for your time and work!

@keplersj
Copy link
Author

@juxuanu Very glad the Flatpak is working well for you! Moving the contents of ~/.config/Bugdom to ~/.var/app/io.jor.bugdom/config/Bugdom should port your previous scores, saves, and preferences.

@jorio
Copy link
Owner

jorio commented Jun 29, 2022

@keplersj Do you have time to take a look at the Bugdom and Mighty Mike flatpaks? I've been getting notifications about them since I released updates for these games.

@jm2
Copy link

jm2 commented Jul 6, 2022

@keplersj in addition to the updates could you also please add Cro-Mag Rally to the set?

@Tagkit
Copy link

Tagkit commented Jul 28, 2022

@keplersj & @jorio Idk if anyone has come forward to test the compatibility of this and the other games on the Steam Deck, but - while I'm still waiting on shipping for mine- I'd be willing to do some tests and suggestions for you both on the compatibility for these games once my Deck comes in. Anything in particular you are looking for / need feedback on? (Honestly this is my first-ever comment on an issue so anything and everything suggested can be useful.)

@jm2
Copy link

jm2 commented Jul 28, 2022

What I've noticed in very short testing is that SteamInput doesn't appear to get passed to the Pangea apps installed through Flathub and launched via Steam on the Deck. The AppImage binaries provided here work without issue.

@jorio
Copy link
Owner

jorio commented Jul 28, 2022

Let's discuss the Steam Deck in a new issue! (#29)

@jorio jorio closed this as completed Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants