One AppImage that works everywhere instead of the two variants
Is your feature request related to a problem? Please describe.
Hi, I noticed that you have two AppImages (GCC and CLANG) instead of just one. Not a big issue... but this is a bit tricky. What should someone choose between the two?
Wouldn't be better to have just one? Maybe one for each architecture?
Describe the solution you'd like
The pkgforge-dev organization provides an unofficial AppImage that also works on musl systems, not just GLIBC. Such runtime has been successfully tested also on distributions of the 2010.
https://github.com/pkgforge-dev/ImageMagick-AppImage
Please take a look to their build and consider to made changes upstream.
Describe alternatives you've considered
None
Additional context
I'm the developer of AM, package manager for AppImages.
Your AppImages have dedicated installation scripts in my database since 2022, and I have named them like this:
- https://github.com/ivan-hc/AM/blob/main/programs/x86_64/imagemagick-clang
- https://github.com/ivan-hc/AM/blob/main/programs/x86_64/imagemagick-gcc
I have left such scripts like this, with their names, and I forgot about them.
Today, one of the members of pkgforge-dev organization lets me notice that its unofficial AppImage have had hundreds of downloads lately... so I remembered of these two scripts I have.
The unofficial AppImage also works on musl systems and is available for x86_64 and aarch64
https://github.com/pkgforge-dev/ImageMagick-AppImage
I was thinking to rewrite a script to choose between multiple sources, with name imagemagick, so people can install it with this name.
But instead of including the unofficial one, what I ask is to review your workflow to have only one AppImage instead of two.
I am a packager of AppImages myself, I have built about 100 of them for x86_64 in my repositories, this is why I asked.
I know how much is hard to have a lot of packages, and I'd like to see you have less work to do. Having two methods for bundle them have its costs, I guess. Using one workflow for one AppImage instead of two would help more you and your users.
Just my two cents.
PS: please let me know if you decide to ship only one package, so I will be able to remove the two already available in AM in favor of the new imagemagick I will add in the database.
Greetings.
Source: ImageMagick/ImageMagick