Morning, IMHO, suffixing our binaries is a kludge. It “solves” the major version transition, but not any of the other use cases such as minor version upgrades, different builds of the same Qt version, etc.
Qt Creator already provides a way to manage and switch Qt versions: https://doc.qt.io/qtcreator/creator-project-qmake.html What we need is a command line tool for doing the same. That’s how other project solve things too (nvm, rvm, pyenv, etc). And we already have a tool for that, qtchooser. If maintenance of that is an issue, then let’s solve that. Why is that not an acceptable solution for distros? Tor Arne On 27 Oct 2020, at 17:34, Thiago Macieira <[email protected]<mailto:[email protected]>> wrote: Have we fixed it? I do not plan on updating qtchooser for Qt 6. Qt 6 should not install any binary with the same name as Qt 5 did. -- Thiago Macieira - thiago.macieira (AT) intel.com<http://intel.com> Software Architect - Intel DPG Cloud Engineering _______________________________________________ Development mailing list [email protected]<mailto:[email protected]> https://lists.qt-project.org/listinfo/development
_______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
