[NTLUG:Discuss] QT upgrade

[Jeremy Blosser]

al_h at technologist.com [al_h at technologist.com] wrote:
> I am planning to upgrade from qt-1.44 to qt 2.0.1
> 
> rpm -Uvh qt-2.0.1...  .rpm
> gives lots of dependency errors about libqt.so.1
> after I upgrade can I simply make a symlink to the new one?

Not the way I think you mean.  Qt 2 and Qt 1 are not binary compatible.
Things that need one will not work with the other in most cases.

First, if you don't have anything that needs Qt 2, don't bother.  ie, don't
think there's a point in upgrading for it's own sake, because there isn't.

If you actually need Qt 2, there are a couple ways to do it -- you can
rpm -ihv --force qt-2.0.1...rpm to have both installed.  The only conflict
is a libqt.so file that exists in both, to point to the default Qt.  But
they'll work without.  You can also get, rebuild, and install the Qt1x and
Qt-2 rpms RedHat made for 6.0.  These were made to allow both to coexist on
the same system.

If you compile things against Qt, the rpm route will only let you have one
of the -devel packages installed (unless you build your own RPMs).  But if
you compile things, you can probably figure out how to get both of them
installed and just use the one you need to compile a given app using
environment variables and options to ./configure.

-- 
Jeremy Blosser   |   jblosser at firinn.org   |   http://jblosser.firinn.org/
-----------------+-------------------------+------------------------------
"If Microsoft can change and compete on quality, I've won." -- L. Torvalds
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 355 bytes
Desc: not available
Url : http://ntlug.org/pipermail/discuss/attachments/19991024/4ad533cc/attachment.bin