Imlib should not depend on GTK when "gtk" is not in the USE variable. Imlib is usable even when compiled without GDK support. For example it will be possible to compile icewm with imlib on systems without GTK if this dependency is optional. A patch to the current ebuild is attached.
Created attachment 11648 [details, diff] makes GTK dependency in the imlib ebuild optional
it's one of those cases where apps depending on imlib expect it to be built with gdk_imlib support and since we can't force use flags on dependencies in portage we prefer to be on the safe side and always have imlib build with gtk support.
Imlib, with this patch in place, does not compile for me unless I USE the 'gtk' flag. It ends with pages of compile errors, thou these select lines from the configure step should tell you what you need to know: checking for gtk-config... /dev/null/bin/gtk-config checking for GTK - version >= 1.2.1... ./configure: line 1: /dev/null/bin/gtk-config: Not a directory ./configure: line 1: /dev/null/bin/gtk-config: Not a directory ./configure: line 1: /dev/null/bin/gtk-config: Not a directory ./configure: line 1: /dev/null/bin/gtk-config: Not a directory ./configure: line 1: /dev/null/bin/gtk-config: Not a directory yes Once I did the following: USE="gtk" emerge -v kde imlib compiled without any problems. - Jason B.
