I had wxGTK 2.6 installed. I emerged -U world, which installed wxwidgets 2.4. This is fine. However, this changed the "default" wx-widgets install to 2.4. By "default", I mean that wx-config (used in Makefiles to find the right include paths and libs) now pointed to the 2.4 libraries. I still have a wx-config-2.6 (or maybe the 2.4 ebuild moved wx-config from 2.6 to wx-config-2.6). After removing wxGTK 2.4, I can make a symlink wx-config -> wx-config-2.6 and get back to work. I would think the principal of least astonishment would be satisfied by having the current default wxGTK *remain* the default wxGTK when another version is installed. The current behavior is surprising and seems wrong to me. I'm sure someone worked very hard to create this fancy wxGTK multi-install system, and I appreciate their efforts. But changing the existing install is a bit too invasive for my tastes and expectations. When I do an emerge -U, I don't expect wxGTK to switch from 2.6 to 2.4. I know emerge -U is deprecated, just like emerging by path, but the alternatives are worse than the risks. I'm not sure if the wxGTK 2.4 ebuild changed anything else. If so, wx-config-2.6 is hiding from me. So the only problem I know of so far is that wx-config was changed from 2.6 to 2.4, even though wxGTK 2.6 was installed first. -Paul Reproducible: Always Steps to Reproduce: 0.Uninstall all wxGTK builds. 1.Install wxGTK 2.6 2.wx-config --cppflags, note that the libs it selects are from the 2.6 install 3.Install wxGTK 2.4, perhaps with emerge -U world 4.wx-config --cppflags, note that libs are from 2.4 install 5.emerge -C wxGTK-2.4...., note that wx-config is now *MISSING* Actual Results: explained above Expected Results: wxGTK 2.4 should *NOT* have changed wx-config. Perhaps it could make a wx-config-2.4, instead of pushing 2.6 out of the way.
Changing to "applications". I think I was drunk when I chose "core". No, wait, maybe I was on drugs. Hard to say, I don't remember much.
*** This bug has been marked as a duplicate of 91307 ***
