dooble
dooble copied to clipboard
What about building to AppImage on Linux?
It's for future releases and not for now, I know you are porting another Qt application to Android. Deb package only applicable on Debian/Ubuntu based systems and on other Linux we have to build from source. Given the nature of Qt building to a plain .tar.gz is not really easy so I suggest building to AppImage. I have seen may Qt application distributed as AppImage, or even more popular, flatpak, but I prefer AppImage more than flatpak, though. This way we will have the deb package for Debian/Ubuntu and AppImage for the rest. AppImage also means it's being portable and doesn't need to be installed, you chmod + x the .AppImage file and just click or double click on it to run.
This reminds me of another ticket. RPM. You can convert a Debian file into an AppImage file.
https://appimage.github.io/deb2appimage/
I dislike working on packaging so I will not be doing this.
1 linked issue ](https://github.com/textbrowser/dooble/issues/60)
I do not understand the universality of this AppImage. Suppose I create an AppImage using Ubuntu 22.04 and someone attempts to install it on Ubuntu 18.04. Will this not fail as there will be inconsistencies with libraries beyond Dooble? Can AppImage preserve backwards compatibility?
"To be able to run on any Linux distribution, an AppImage should bundle all the resources it needs at runtime that cannot be reasonably expected to be “there” in the default installation of all still-supported target systems (Linux distributions). The most common resources are the actual binaries, shared library dependencies, icons and other graphics and of course one or more desktop files for desktop integration."
This is an unreasonable expectation.
So this is dead and no one is volunteering!