I currently run media-gfx/gimp-2.99.18-r1[-X] but have x11-libs/cairo and x11-libs/gtk+ built with the X USE flag. This combination works fine for me, but as of >=media-gfx/gimp-2.99.18-r2 no longer satisfies Gimp's dependencies, since it depends on [X=] for Cairo, GTK+, Pango and libwmf. That means I'll need to build Gimp with X (which I don't need/want) or Cairo and GTK+ without X (which breaks other packages). Reading the discussion in bug 942358 there is no indication that Gimp built without X does not work correctly when Cairo/GTK+/Pango/libwmf are built with X. I believe Gimp's [X=] USE dependencies should be replaced with [X?]. Reproducible: Always Steps to Reproduce: 1. USE=X emerge x11-libs/cairo x11-libs/gtk+ 2. USE=-X emerge '>=media-gfx/gimp-2.99.18-r2' Actual Results: Portage refuses to build Gimp. Expected Results: Gimp gets compiled.
Created attachment 908358 [details] emerge --info
> I believe Gimp's [X=] USE dependencies should be replaced with [X?]. No. The gimp[-X] fails to built with gtk+[X] etc. Initially I think about [X?] flags but then gimp[-X] failed on configuration phase (pkgconfig etc) or later with others x11-libs/*[X] or its x11-libs/*[X] dependencies. To test it I switched to wayland session and remove some x11 libs that are required. Otherwise it will require to "fix" gtk+, pango, cairo, libwmf. > I currently run media-gfx/gimp-2.99.18-r1[-X] but have x11-libs/cairo and x11-libs/gtk+ built with the X USE flag. But why? The gimp[X] bring additionnaly xcursor library and others are already presented in the system in your case.
> media-gfx/gimp-2.99.18-r1[-X] I.e. this only brings libXcursor feature while gimp-2.99.18-r2 fix additional x11-libs/* optional dependensies e.g. for wayland session. I thought about separate USE="xcursor" but desides it's too tiny to split it from USE="X".
(In reply to Sergey Torokhov from comment #2) > > I believe Gimp's [X=] USE dependencies should be replaced with [X?]. > > No. The gimp[-X] fails to built with gtk+[X] etc. Initially I think about > [X?] flags but then gimp[-X] failed on configuration phase (pkgconfig etc) > or later with others x11-libs/*[X] or its x11-libs/*[X] dependencies. To > test it I switched to wayland session and remove some x11 libs that are > required. Otherwise it will require to "fix" gtk+, pango, cairo, libwmf. Well, I suppose you did better testing than I did. I successfully build Gimp with -X, but I'll admit that the dependencies of that flag happen to be installed on my system. Seems like I unknowingly built it with X11 support anyway. > > I currently run media-gfx/gimp-2.99.18-r1[-X] but have x11-libs/cairo and x11-libs/gtk+ built with the X USE flag. > > But why? The gimp[X] bring additionnaly xcursor library and others are > already presented in the system in your case. I mostly use Wayland-native applications and therefore disable the X USE flag globally. I enabled it for the few packages that actually need it. It struck me as odd that I now need to enable X on Gimp (and Pango) so that I can have it enabled on GTK+ and Cairo. I still think this is not ideal, but if there's no way to overrule the magic in Gimp's build system, feel free to close this bug.
(In reply to Sebastian Hamann from comment #4) > (In reply to Sergey Torokhov from comment #2) > > > I believe Gimp's [X=] USE dependencies should be replaced with [X?]. > > > > No. The gimp[-X] fails to built with gtk+[X] etc. Initially I think about > > [X?] flags but then gimp[-X] failed on configuration phase (pkgconfig etc) > > or later with others x11-libs/*[X] or its x11-libs/*[X] dependencies. To > > test it I switched to wayland session and remove some x11 libs that are > > required. Otherwise it will require to "fix" gtk+, pango, cairo, libwmf. > > Well, I suppose you did better testing than I did. > I successfully build Gimp with -X, but I'll admit that the dependencies of > that flag happen to be installed on my system. Seems like I unknowingly > built it with X11 support anyway. Have not dug into this, but this feels suspiciously similar to Bug 942352 and Bug 903707. There's some automagic stuff going on there as well that causes the build to fail if some x11-libs/* are built with +X.
Yes, it looks similar with my case. I'm thinking about to retry build gimp that way to reproduce it and when put logs here.
