amule uses the "gtk" useflag to mark if the wxGTK GUI will be built. This gives bad results, at least on my system. the "gtk" useflag is for gtk 1.x apps, and therefore disabled here, i have only gtk2 set. So wxGTK is built with gtk2 support. the amule ebuild looks for the gtk useflag, which is unset and assumes not to build the gui. Therefore the ebuild tries to do "need-wxwidgets base" which fails here,because i have no "base" wxWidgets, but a gtk2 one. So the ebuild does not even build here! Perhaps a solution would be to simply use the gtk2 flag instead of gtk, but this could cause the same problems because wxGTK can also be built with gtk 1.x support. so some more fine grained controll checking several (gtk2,wxgtk1 and gtk?) use flags should be used instead. Btw,why isn't the pkg_setup code in the amule ebuild not part of an eclass? looks pretty general to me.
(In reply to comment #0) > system. the "gtk" useflag is for gtk 1.x apps, and > therefore disabled here, i have only gtk2 set. So wxGTK is built with gtk2 > support. the amule ebuild looks for the gtk useflag, which is unset and assumes > not to build the gui. gtk use flag is *not* used for gtk-1* any more and you should enable it; gtk2 use flags is deprecated and is being removed from all ebuilds. See Bug 106560.
