Qt 3.2 requirement

[Chris Howells]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Friday 25 July 2003 06:33, Ralf Nolden wrote:
> I guess the only thing that currently prevents that pretty much is the
> rumours about KDE 3.1.x not working correctly with Qt 3.2. I've build Qt

Maybe I'm missing something in which case I apologise, but _why_ does it 
matter that Qt 3.2 doesn't work with KDE 3.1?

We don't expect KDE 3.0 to work with Qt 3.2 so why 3.1?

If developers are running HEAD and all its brokenness/unstableness, I don't 
think it's unreasonable to expect them to use a different Qt; it's not 
exactly difficult to build and get thanks to qt-copy.

> 3.2 from scatch to test that and replaced qt-3.1.2 on a test machine with
> KDE 3.1.2 with it to see how it works out. I can't see any odd behaviors or
> anything that wouldn't allow us to switch to Qt 3.2 generally, so the
> question is: what are the "bugs" that Qt 3.2 would trigger in a KDE 3.1.x
> environment ?

I'm sure there are bugs and I don't think that those bugs would transpire 
without most of the developers testing Qt 3.2 with KDE 3.1.x which I doubt it 
going to happen, ever.

- -- 
Cheers, Chris Howells -- chris at chrishowells.co.uk, howells at kde.org
Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C
KDE/Qt/C++/PHP Developer: http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/IO37F8Iu1zN5WiwRAhHHAKClG8lP6XGewLOGTXQyNZpGVHLg9ACeJk99
PPzW4oYlBBB8VnXwychMYrY=
=JWQU
-----END PGP SIGNATURE-----