there is a new qt-version, but the qt-x11-free-3.0.5-ko_input.patch doesn't succeed. ebuild can be copied from qt-3.0.5-r2. qt-3.0.6 is a bugfix release, it is binary compatible to 3.0.5.
I don't think I really want qt 3.0.6. It's been around for a while but I've refrained from putting an ebuild in portage because kde 3.1, which should be released in a month or less, will absolutely require qt 3.1, which should be released before then. I want to make the change straight to qt 3.1, without testing etc. qt 3.0.6 in between. So unless there's some specific reason users really want 3.0.6 (some important bugfix), I'd like to skip it. Actually, I was rather frightened of 3.0.6 a while ago because of all the BIC qt3.1 mess. That's resolved now but qt 3.0.6 is still described on the trolls' page as: --- Binary compatibility warning: Qt 3.0.6 is backward and forward binary compatible with Qt 3.0.5, and is planned to be binary compatible with Qt 3.1. Unfortunately Qt 3.0.5 is not 100% backward binary compatible with Qt 3.0.3 (a class got a few bytes smaller), meaning executables compiled with 3.0.5 may not run properly when linked dynamically to 3.0.3. at runtime. Note that this is not a problem on MS-Windows. Due to its wide distributed in various GNU/Linux distributions, we have decided to stick with 3.0.5's ABI. If you ship dynamically linked executables, we suggest putting a QT_REQUIRE_VERSION macro at the beginning of your main function. --- So things seem clear now since we've completed the upgrade from 3.0.3 to 3.0.5, but still I'd rather not have too many versions about if I can help it. Comments anyone?
i will also be happy with qt-3.0.5 and a bump to qt-3.1. (but if an user wants qt-3.0.6, he should get it ;)
well, qt-3.1 is in portage, no need for 3.0.6
*** Bug 10896 has been marked as a duplicate of this bug. ***
