> As a side-effect which I'm interested in, TQT3 should be
> able to co-exist under "/usr" with any distribution-provided
> QT3 and/or QT4 version.
> So, legacy QT3/KDE3 programs shipped with the distro will
> use the legacy QT3, KDE4 programs will use QT4, and TDE will
> use TQT3, and everyone should be happy :)

I too am interested in complete installation compatibility. :) One challenge is the bin files in Qt3 are the same as those in Qt4. That is not a problem per se, but is confusing, especially when creating sym links in /usr/bin.

> On my current TDE 3.5.13 build, it looks like the QT
> 3.3.8.D, that I've packaged as an update to the
> distro-provided QT 3.3.8.B, makes some legacy QT3 programs
> crash, but I do not know why.
> As I understood, QT 3.4.0 for future TDE R14 will officially
> break compatibility with QT 3.3.8, so having both QT3.3.8.B
> and TQT 3.4.0 at the same time is mandatory for me.

As I recall, whatever was done from 3.3.8.c to 3.3.8.d was strictly Trinity related and broke backwards compatibility. Our own Qt3 change log is, um, vague as to the specific changes and the reasons for breaking backwards compatibility. Regardless, KDE3 apps cannot use Qt3 3.3.8.d. Non KDE3 Qt3 apps might still work, but would need to be recompiled against 3.3.8.d rather than the original 3.3.8.b.

In our proposed FAQ we discuss backwards compatibility but we really do not address the technical aspects. :(

Darrell