Just adding "gnome? ( foo bar )" doesn't suffice. The build script automagically detects and builds with it, even though the gnome use flag is not set.
Yep, I suspect this being an issue with most of gtk apps, as when you mistakenly let some gnome dependancies in, if you remove them you'll need a lot of work/re-emersion to have gtk apps working fine (this is a bit viral). Some examples? Gimp, inkscape ,avidemux.... The only serious solution to this issue I found was to mask any gnome-* package in my system to be warned when something want to pull it in, so I can choose if unmask... (the alternative would be `config --without-lib` mechanism where lib are the gnome deps).
In fact, the problem is that the gimp configure script automagically detects a bunch of libs. I once reported this upstream and got basically the answer "we don't care". Feel free do write patches.
I made two patches, one for gimp's configure.in, and one for latest unstable ebuild. I tested them on my system and it was fine, but I'm still not sure whether my changes are correct. Uploading patches just now...
Created attachment 105008 [details, diff] automagic.patch
Created attachment 105009 [details, diff] gimp-2.3.13.ebuild.patch
Have sent the patch upstream, hope this will get in before 2.4.0, else I'd patch in the ebuild: http://bugzilla.gnome.org/show_bug.cgi?id=425267
*** Bug 164820 has been marked as a duplicate of this bug. ***
fixed in 2.3.16 and -9999
