In wxGTK 2.5.3, GTK2 is enabled by default, therefore you will never be able to install GTK 1.2* support with this ebuild. To install a GTK 1.2* version you need to pass a --disable-gtk2 flag to the configure script. Another issue is whether GTK 1.2* should be installed by default, when the wxGTK developers choose not to.
Did you resync in the last few hours? This bug is fixed in the ebuild I've got on my system. if ! use no_wxgtk1 ; then [...] ../configure ${myconf} --disable-gtk2 `use_with odbc`\
I just synced and yes it is fixed. The bug in wxwidgets.eclass is still there, but it has nothing to do with this bug.
The reason it installs gtk1 by default is because as of right now some wx apps don't work with gtk2, some only work with gtk2-non-unicode and some work fine with gtk2-unicode. When stable 2.6 is released, I think installing just gtk2-unicode by default and having a special flag to install gtk1 also would be preferred. Its a mess though, because we'd have two different ways to install the same package in different SLOTs. If you guys have any ideas on this, please speak up.
I understand and agree for the moment. wxGTK still use alot of deprecated GTK code and until that is brought up to date we will not have stable GTK2 support. Threading in wxGTK is very buggy (also with gtk1), but hopefully that will be fixed in one of the next releases.
*** Bug 71147 has been marked as a duplicate of this bug. ***
