1 |
Am Sa., 30. Nov. 2019 um 11:34 Uhr schrieb Mick <michaelkintzios@×××××.com>: |
2 |
|
3 |
> On Saturday, 30 November 2019 07:17:01 GMT Franz Fellner wrote: |
4 |
> > inkscape-0.92.4 has the same issue. |
5 |
> > The problem is that the API (Programming interface, not Binary interface) |
6 |
> > between imagemagick-6 and imagemagick-7 isn't compatible. |
7 |
> > And inkscape never was updated to use the API from imagemagick-7. |
8 |
> |
9 |
> Yes, that's exactly the problem. |
10 |
> |
11 |
> media-gfx/inkscape-0.92.4 which is presently the stable version is quite |
12 |
> happy |
13 |
> with media-gfx/imagemagick-7.0.9.5. |
14 |
> |
15 |
|
16 |
Ah. It's 7.0.8.5, not 7.0.9.5: |
17 |
https://bugs.gentoo.org/663468#c5 |
18 |
Some deprecated features of the API were removed. Unfortunately also the |
19 |
pkgconfig file was renamed to Magick++ which made inkscape silently disable |
20 |
imagemagick support and the compilation failure/incompatibility wasn't |
21 |
noticed for a long time. |
22 |
|
23 |
|
24 |
> However, the unstable version of inkscape-1.0_beta1 requires imagemagick |
25 |
> versions prior to 7.0.9.5, with the currently available version of |
26 |
> imagemagick-6.9.10.74 fulfilling the requirement. |
27 |
> |
28 |
|
29 |
imakemagick-7.0.8.5, again. Not that nobody will stay confused. |
30 |
|
31 |
|
32 |
> > 1) entirely disable imagemagick for inkscape, e.g. with |
33 |
> "media-gfx/inkscape |
34 |
> > -imagemagick" in package.use |
35 |
> |
36 |
> If you do this, you'll find that conversions and imports/exports from one |
37 |
> graphics file format to another would be somewhat limited. Imagemagick |
38 |
> relies |
39 |
> on inkscape for this functionality. |
40 |
> |
41 |
|
42 |
The other way around, inkscape needs imagemagick for such conversions. |
43 |
|
44 |
I don't know how limiting it will be. If all you want to do is create pure |
45 |
vector graphics you are good to go. |
46 |
|
47 |
> 2) Use inkscape-1.0.0_beta1 and enable both USE-Flags "imagemagick |
48 |
> > graphicsmagick". |
49 |
> > That way you will get the imagemagick features through |
50 |
> graphicsmagick, |
51 |
> > which means imagemagick is not a dependency of inkscape anymore. |
52 |
> |
53 |
> Right, but graphicsmagick is more limited in its functionality than |
54 |
> imagemagick. For a poweruser of imagemagick this may present a problem - |
55 |
> but |
56 |
> I don't know how big a problem it might be. |
57 |
|
58 |
|
59 |
You aren't forced to build graphicsmagick as a complete replacement for |
60 |
imagemagick. |
61 |
You only need the C++-API for inkscape and not the commandline tools. |
62 |
Put "media-gfx/graphicsmagick cxx -imagemagick" in your package.use and |
63 |
imagemagick and graphicsmagick can be installed at the same time. |