On Tuesday, 13 November 2018 15:19:58 PST Lisandro Damián Nicanor Pérez Meyer wrote: > Agreed, but this means that if an application is backwards compatible then > it must be kept like that for all the Qt 6 lifetime. Is that feasible?
Yes. Assistant, Linguist, the D-Bus tools should be. But I've just remembered that Designer loads plugins and those are quite clearly tied to the Qt version. The file format is backwards compatible and has remained so for a few years. It is possible that the plugins generate the same XML regardless of version, but I think we shouldn't risk it. So yes, Designer should be versioned. > > That only leaves front-end tools that are intricately tied to the Qt > > version that need renaming. The only two I can think of that fits this > > description are the "qml" and "qmlscene" pair. If we're feeling nice, we > > can do it too for diagnostic tools, like qtdiag, qtpaths, qtplugininfo. > > It would probably be the safest thing to do. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
