On Saturday, 30 November 2019 07:17:01 GMT Franz Fellner wrote: > inkscape-0.92.4 has the same issue. > The problem is that the API (Programming interface, not Binary interface) > between imagemagick-6 and imagemagick-7 isn't compatible. > And inkscape never was updated to use the API from imagemagick-7.
Yes, that's exactly the problem. media-gfx/inkscape-0.92.4 which is presently the stable version is quite happy with media-gfx/imagemagick-7.0.9.5. However, the unstable version of inkscape-1.0_beta1 requires imagemagick versions prior to 7.0.9.5, with the currently available version of imagemagick-6.9.10.74 fulfilling the requirement. The inkscape package is the dog and imagemagick (a dependency) is the tail. Usually the dog wags the tail and not the other way around. However, portage is asking for inkscape to be keyworded to a testing beta version for what appears to me to be no good reason. Portage should keep inkscape at the stable 0.92.4 version, with imagemagick at 6.9.10.74, on a system which is running stable packages. > That's why you are forced to downgrade imagemagick to a version lower than > 7 when you want to use imagemagick in inkscape. > If you want to stay with imagemagick >=7 you have two options: > 1) entirely disable imagemagick for inkscape, e.g. with "media-gfx/inkscape > -imagemagick" in package.use If you do this, you'll find that conversions and imports/exports from one graphics file format to another would be somewhat limited. Imagemagick relies on inkscape for this functionality. > 2) Use inkscape-1.0.0_beta1 and enable both USE-Flags "imagemagick > graphicsmagick". > That way you will get the imagemagick features through graphicsmagick, > which means imagemagick is not a dependency of inkscape anymore. Right, but graphicsmagick is more limited in its functionality than imagemagick. For a poweruser of imagemagick this may present a problem - but I don't know how big a problem it might be. While I was chasing my tail around this clash hoping portage would eventually get it right, I seem to recall a more recent combo. When inkscape-1.0_beta1 is keyworded, portage is asking to also keyword imagemagick-*9999. I assume the trunk has a version which works with inkscape-1.0_beta1, but I'm not sure. For now I just exclude inkscape from upgrades until the dust on this settles. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
