ImageMagick / ImageMagick/ImageMagick
Feature: Add static linux build archive to release assets
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.5k
- Forks
- 1.7k
- Avg merge
- 10h 17m
- Merged PRs (30d)
- 28
Description
Is your feature request related to a problem? Please describe.
Reason
Not all dependency management tools support AppImage
Example
Project uses mise-en-place mise use imagemagick to have crossplatform ImageMagick dependency.
On Windows, mise uses GitHub ImageMagick releases from aqua registry: https://github.com/aquaproj/aqua-registry/pull/50281
On Linux, mise falls back to much slower and error-prone conda, because mise doesn't support AppImage: https://github.com/jdx/mise/pull/10118
Describe the solution you'd like
It would be great help to have a static build archive for Linux that can be installed by common tools like mise directly from GitHub release assets
Describe alternatives you've considered
Current alternative is to use much slower and error-prone conda to install ImageMagick as a project/env dependency
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how Linux builds are produced and how current GitHub release assets are assembled. Determine the requirements for a static Linux archive that common dependency tools can consume, then verify that the archive is generated and published with releases without disrupting existing assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, github, linux
- Domain
- build-system, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100