wxGTK-2.6.0 was released (bug# 89937). If two versions are installed (2.4 & 2.6) /usr/bin/wx-config is a symlink to a 2.4 config. Although 2.6 is the latest stable version upstream, most of the 30+ packages in portage expect /usr/bin/wx-config and will all need to be changed before wx-config is used by 2.6 by default. I did change the ebuild before it went in portage so if only 2.6 is installed it will have a /usr/bin/wx-config symlink. I'll put a /usr/bin/wx-config-2.6 in as suggested while I start going through every package and either changing them or filing bug reports. The reason /usr/bin/wxrc-2.6 exists is because I didn't know it was compatible with 2.4. There is still a problem though because packages shouldn't own files with the same name in case one gets unmerged. That can be overcome with pkg_postrm though, which is what I'll do here by copying a version back after one is removed. So today I'll do those two things (move to a single wxrc and add /usr/bin/wx-config.2.6) and leave this open as a metabug for all packages needing to move to /usr/bin/wx-config-2.4
Read the doc about wxGTK. "The best and safest way to upgrade the wxWindows is to uninstall the old one, and install the new one." http://www.wxwindows.org
I installed wxgtk-2.6 (I don't have 2.4), and then emerged amule-2.0.0_rc7, but I got the following error: !!! set-wxconfig: Error: Can't find normal or debug version: !!! set-wxconfig: /usr/bin/wxgtk-2.4-config not found !!! set-wxconfig: /usr/bin/wxgtkd-2.4-config not found !!! You need to emerge wxGTK with wxgtk1 in your USE What's the problem?
The dependencies on amule <2.0 should be changed to =wxGTK-2.4*. see bug# 71108 for an amule ebuild that works with 2.6*
*** Bug 93957 has been marked as a duplicate of this bug. ***
*** Bug 107251 has been marked as a duplicate of this bug. ***
*** Bug 108012 has been marked as a duplicate of this bug. ***
Over a year has passed and things need to be handled a bit different now for resolving the SLOT issues. Notably most if not all packages use the wxwidgets eclass properly by now, and things should be handled a bit different to overcome COLLISION_PROTECT errors. More in bug 142465 *** This bug has been marked as a duplicate of 142465 ***
