On Wed, 23 Nov 2022 20:16:55 +0000, Joachim Reichel wrote: > > [...] Now I'm wondering if changing the runtime dependency to > > "graphicsmagick-imagemagick-compat | imagemagick" would achieve the > > same while allowing the user to choose (or keep) one of the two > > implementations? > good point!
Thanks :) > I noticed that imagemagick contains mogrify-im6.q16, but missed > that it makes that available as mogrify via the alternatives system. Yeah, this looks a bit complicated with plain imagemagick, versioned imagemagick-something packages, and then graphicsmagick-imagemagick-compat which Conflicts/Replaces/Provides imagemagick. > Since graphicsmagick uses "gm" and ...-compat is "just" a compatiblity > package, I'm even considering using > "imagemagick | imagemagick-6.q16hdri | graphicsmagick-imagemagick-compat" > (different order plus ...hdri variant). Sounds good as well. (Personally I'd be a bit wary about packages with versions in their name but that's just my personal taste.) Thanks again, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `-
signature.asc
Description: Digital Signature
