-
Notifications
You must be signed in to change notification settings - Fork 70
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
Link an appImage official package for releases #270
Comments
At the Minetest gitlab mirror, AppImages are generated by the CI, see for example https://gitlab.com/minetest/minetest/-/jobs/3699400271/artifacts/browse. |
good, I think they are official, but seems to me are generated by commit, so are for git master only. |
After selecting a tag at gitlab it is possible to download an AppImage for an older Minetest release from the build artifacts. The AppImages on gitlab are the only official ones which I'm aware of. |
Did you know how to find the tags on gitlab related to stable release? |
found: https://gitlab.com/minetest/minetest/-/tags |
found:
|
at this point, I'm curious why on the official web site is not linked the AppImage already built for releases? |
Because it's not recommended, Flatpak is currently our only recommended cross-distro format. Snap used to be recommended as well but it became unmaintained. In order to recommend the appimage, we'd need to move away from GitLab (as it's unreliable for builds) and add support for updating
It's 26.7 MB |
happy to see 27 MB, I just try the suggested install command, it show:
this is 1.1 GB of install, mostly are already installed as native distro packages |
The runtime and other dependencies are shared across most Flatpak packages you install in the future. Therefore, installing additional Flatpaks after the Minetest Flatpak will not result in a 1+ GB download (unless the package is using an older runtime). |
take care that as comparison, the AppImage is 60 MB, and work quite the same |
If you install dozens of AppImages, the combined size will eventually be larger than Flatpaks for the same applications as libraries have to be duplicated a lot more often. |
OK, but I think users prefer native distro package to avoid all that drawbacks. AppImage or Flatpak are to have a few updated package, not dozens |
I think for games this size overhead is negligible because often there are large files which are not shared with other programs, e.g. the game's music, images and other media files. Furthermore, if the AppImage is published with a .zsync file, updating a previously downloaded AppImage file usually requires much less download time than updating a package installed with, for example, apt-get or pacman.
It looks like the list of packages shown above includes a nvidia driver and VAAPI. Can this cause compatibility problems? |
No, as driver Flatpaks are only installed if needed on your system. |
outdated unofficial Appimage on 2025. |
Problem
I saw on web site, the official last version for Linux is supplied as Flatpack.
This is enormous package, how is big?
Solution
Please add an official AppImage package.
Alternatives
I saw there are unofficials updated package available like this good:
https://appimage.github.io/Minetest/
but official package is better
The text was updated successfully, but these errors were encountered: