If I were to "correct and revise" my remarks about "not caring" about binary compatibility (much or at all), a couple people make good points about the Linux Standard Base (LSB) and Linux packages/distributions/RPMs. Yes, binary compatibility is more significant in that respect.
IMHO, Mihail made a good point: I think the diff views arise form the fact that Qt lacks unified > redistributable across platforms (even on the same platform, like Windows). > > If there was such redist, a binary compat will be critical, because the > user can freely upgrade (a system-wide) platform, without being scared about > some apps stop working. > In part because of how Qt isn't doing the "unified redistributable" thing, and because the push is for smaller "packages" within the Qt codebase, I'd push for more static-libs linking in the Qt codebase. As others mentioned, I don't typically trust binary compatibility, you can still get a "link error" with interface compatibility, and I'd use that extra hard drive space to not deal with "tweaky-incompatibility" problems by simply statically-linking Qt into my application. Yes, I'm desktop, it may be a different issue for mobile. Yes, if you have zillions of KDE apps, you may "prefer" they all share the new Qt upgrade. However, if all your apps don't work right, or rely upon different Qt versions, then it's possible that didn't buy you as much as you hoped. --charley
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
