Happy 14th birthday, bug!
A lot has happened in the last 14 years, but one thing hasn't changed:
end-user tools written in Perl need something providing Image::Magick,
and if graphicsmagick-libmagick-dev-compat satisfies that then all the
development libraries for other toolchains are pulled in, unnecessarily.
One thing that has changed in the last 14 years is tooling, and the rise
of popularity of containers (docker, etc.). With that has come a renewed
focus on the footprint of images. For an image I'm working on right now,
the following are the size differences for the two providers of
Image::Magick for perl:
libimage-magick-perl: +29.1 MB
graphicsmagick-libmagick-dev-compat: +94.2 MB
I respectfully submit that it still makes sense to split this package.
Current maintainers, do you agree? Would you accept patches to do this,
perhaps after Bullseye?
Best wishes,
--
👱🏻 Jonathan Dowland
✎ j...@dow.land
🔗 https://jmtd.net
