how to prevent binary incompatibilities with libraries (in reference to Bug#320029)
I need some help with finding a good resolution for Bug#320029.
In summary, the current version of my 'librmagick-ruby' package was
compiled against libmagick6-dev_6.0.6.x. It works nicely when run with
libmagick6_6.0.6.x, but fails when libmagick6 is upgraded to the version
currently in unstable (6.2.3.x).
I have to admit that I don't understand the implications of the failure;
does this mean that ABI compatibility has been broken, ie. that there's
a bug in the libmagick6 package?
My package currently Depends on libmagick6, sans version number. The
bug reporter suggested that I depend on a specific version - a thought
that had also occurred to me - but I'm not sure that it's the best thing
to do. What do you think?
I'm not sure how I'd inject a version-number into the libmagick6,
wayway, since it's generated by ${shlibs:Depends}. That's another thing
that confuses me: why does the generated dependency not include version
info?
Thanks in advice for your advice, tolerance, personal abuse, or
irrelevant anecdotes.
--
cheers, MikeW http://www.dogbiscuit.org/mdub/
Reply to: