I've been encountering a few problems in the Qt GUI toolkit (version
2.1.0beta1). Specifically, there are bugs in the beta version that are
affecting certain apps (notably, licq) that I'm using.
I've been following threads concerning these problems on the licq mailing
list, and the consensus is that the most recent release of Qt (that is, the
2.1.0 release, which is now out of beta) corrects these problems.
Indeed, I took the qt-2.1.0-4.beta1.src.rpm, changed it to use the
production release of Qt 2.1.0, and then rebuilt it. It corrects the licq
problems I've been experiencing, and so far, I've encountered no side
effects.
Please consider releasing a qt-2.1.0-5 RPM as a 6.2 Bug Fix update. This
would make me happy (I try not to deviate from standard Red Hat releases if
I can help it; it makes it too much a pain to keep track of how my system
differs from the standard release system), and would make people happy who
have neither the skills nor inclination to update their RPMs themselves.
;)

Thanks - it's fixed in Rawhide (using 2.1.1 with some minor fixes).
We can't release an update for 6.2 because that would require releasing updates
for all packages linked to it - they're not fully binary compatible
unfortunately.

Comment on attachment 223[details]
Spec file patch
Comment moved from attachments description:
BTW, here are the changes I needed to make to the spec file. The "make
symlinks" addition (to remake all of the symlinks in the "include"
subdirectory) is important; the qt-x11-2.1.0.tar.gz distribution comes with a
pre-built "include" subdirectory that has two symbolic links (qt_mac.h and
qt_windows.h) that point to non-existent files. If those bogus
symlinks are not removed (which the "make symlinks" step takes care of), the
"install" phase of building the RPM will fail.

Note

You need to
log in
before you can comment on or make changes to this bug.