-
Notifications
You must be signed in to change notification settings - Fork 21
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
Output appimages on CI #123
Comments
Seems like it is not officially available on some distros (e.g. Arch). So we should provide AppImage as additional instead of removing Flatpak. |
How about... We make Flatpaks for Flathub hosting. |
We can publish to Flathub for the stable release. For development build we should not publish to Flathub and provide only bundle files and AppImage on CI. |
Just to chip in: in the past I've made a few AppImages of Qt5 apps with https://github.com/probonopd/linuxdeployqt for both Linux and ChromeOS. I used qmake instead of CMake though, yet documentation says CMake is supported too. AppImage should work just fine on any distro. Internally it's just an archive that mounts itself via fuse2 to its own fs mount point with every dependency included except GLibC. |
Interesting. Let's try adding AppImage and see how it works. If no any issues we can remove Flatpak. |
Great. @VocalFan can I take this one? |
If you were waiting for confirmation... Yes. Unless if I say I'll do it... Anyone else can! :3 |
I started work already but |
So, this is really dead. |
Now our binary don't need fancy dependencies so it can run directly without Flatpak or AppImage. See #1140 for the PR that switched to this. |
AppImages are usually easier to use than Flatpaks. (Just double-click to run!)
They also include all of the dependencies and are usually smaller than flatpaks or snaps. All the user would have to do to use Obliteration on linux would be to download the AppImage, and double click.
The text was updated successfully, but these errors were encountered: