Sun Apr 1 04:52:00 GMT 2012
On 2012-03-31 05:26, Corinna Vinschen wrote:
> I'm a bit puzzled. Version 220.127.116.11 came with a library package called
> libMagick10. 18.104.22.168 came with a library called libImageMagick1, and
> now we get libMagickCore5.
> Is there some secret scheme behind the changing library names?
Previously the actual libraries were named libMagick (low-level core),
libWand (high-level API), and libMagick++ (C++ bindings). Starting with
22.214.171.124 (yes, a patch release), the first two were changed to
libMagickCore and libMagickWand, and the ABI versions reset (even though
the C++ library wasn't renamed!).
When the last maintainer packaged 126.96.36.199, instead of calling it
libMagick1, he called it libImageMagick1 to avoid conflicting with older
versions when the ABI numbers jumped again (remember, there was a
libMagick6 package way back when, and sure enough, they're at ABI 5 again).
I never liked the libImageMagick1 naming, for two reasons: 1) there is
no library named "libImageMagick", and 2) it doesn't match the name of
the -devel package. So I was planning to use libMagickCore5 instead and
ITA it due to the previously announced security vulnerabilities, then
Marco beat me to it (which is just fine with me).
> And, after uploading 188.8.131.52-1, can we remove 184.108.40.206 together with
> libMagick10, given that it's not used by any package in the distro?
Absolutely, and once autotrace and pstoedit are rebuilt, libImageMagick1
should go as well due to the security vulnerabilities.
More information about the Cygwin-apps