Hi Ken,
I'm not one of the developers, but as far as I know, only Inkscape extensions can currently depend upon IM. A quick search in my current extensions directory (the ones that come with Inkscape) shows that only the webslicer extension seems to have an optional dependency upon IM, for jpg and gif export.
So from this, I would conclude that for normal Inkscape usage, IM version is (mostly) irrelevant, but that if you install an externally created, user-contributed extension, that one may be incompatible (as this one seems to be for Windows, as a result of im fixing the problem with Windows having a 'convert' function already: https://github.com/giacmir/Inkscape-JPEG-export-extension/issues/14).
Please someone correct me if I'm wrong :)
See also: http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies
Regards, Maren
Am 05.12.2016 um 03:57 schrieb Ken Moffat:
There was a report to BLFS that not all packages which could use ImageMagick recognized the changes in IM7. So we reverted to IM6. Now that I've had time to look at this, inkscape is a major package in this category. ImageMagick-7 has changed a lot of things. And as somebody who uses ImageMagick tools, I don't want to be stuck with the old version.
Can I fix that ? Probably not, particularly with the move to cmake (I have no idea how to deal with different versions of a package in cmake, unlike configure scripts where there are usually things to copy).
Perhaps I can start to take a look when I get some time. But what I will need is an idiot's guide to what IM brings to inkscape, so that in the (unlikely) event that I produce a patch I can test it to see if it works. For the moment, all I know is that inkscape can use IM
- but the details/benefits elude me.
Any pointers, pretty please ?
ĸen