Hi @RTimothyEdwards ,
The 8.3.683 release ships four AppImages (appimage/7, appimage/8, appimage/9, appimage/10), presumably corresponding to different glibc baselines. While this maximizes compatibility, it means four separate builds, four separate uploads, and four artifacts to maintain for every single release.
The Anylinux-AppImage toolchain (https://github.com/pkgforge-dev/Anylinux-AppImages) is designed exactly to solve this: it produces a single AppImage that runs across all major GNU/Linux distributions, using a portable runtime rather than a per-glibc build matrix. That would replace the four-variant approach with one build and one artifact per release.
As a bonus, a single AppImage also makes it trivial for downstream installers like AppMan (am) to ship Magic effortlessly, since there'd no longer be any ambiguity about which variant to pick.
Hi @RTimothyEdwards ,
The
8.3.683release ships fourAppImages(appimage/7, appimage/8, appimage/9, appimage/10), presumably corresponding to differentglibcbaselines. While this maximizes compatibility, it means four separate builds, four separate uploads, and four artifacts to maintain for every single release.The
Anylinux-AppImagetoolchain (https://github.com/pkgforge-dev/Anylinux-AppImages) is designed exactly to solve this: it produces a singleAppImagethat runs across all major GNU/Linux distributions, using a portable runtime rather than a per-glibc build matrix. That would replace the four-variant approach with one build and one artifact per release.As a bonus, a single AppImage also makes it trivial for downstream installers like AppMan (am) to ship Magic effortlessly, since there'd no longer be any ambiguity about which variant to pick.