From: David Evans Date: 8 January 2017 at 00:43:46 > While you do this, I'll make a list of other inkscape dependencies from my > (working) installation that need to be rebuilt with +quartz.
FWIW, here is the result of starting with my non-working version of inkscape (which does not trigger xquartz startup btw), running port -q rdeps --no-build --index inkscape and then running port -q installed on each reported dependency, and finally grepping for x11: gdk-pixbuf2 @2.36.3_0+x11 (active) cairo @1.14.8_0+quartz+x11 (active) pango @1.40.3_1+quartz+x11 (active) cairomm @1.10.0_3+quartz+x11 (active) pangomm @2.36.0_0+quartz+x11 (active) ImageMagick @6.9.6-6_0+rsvg+x11 (active) giflib @4.2.3_0+x11 (active) ghostscript @9.19_0+x11 (active) I assume ImageMagick and ghostscript are harmless in this context. But gdk-pixbuf2? It has no quartz variant. On a different note, I had assumed, perhaps too naïvely, that this sort of problem is what a package system is supposed to protect against. Since it appearently doesn't, is the underlying problem that the problem is too complex to be handled by a dependency system like macports's? This is the sort of problem that makes the nix package system look more attractive. Though it may also be (a lot?) harder to use. – Harald
