It was determined from
https://salsa.debian.org/qt-kde-team/qt/qtchooser/-/merge_requests/2 and
a downstream Ubuntu bug on Qt6 not working that QtChooser is dead
upstream on purpose.

If it is dead upstream on purpose and should NOT work with Qt6, could we
add a Breaks on qt6 and higher, since it is only kept around for Qt5
support and not breaking Qt5 applications that rely on it?  Therefore
indicating that Qt6 is not and *will* not be supported on the
now-dead-upstream project?

(I'm only caring because this bug ended up on the Ubuntu lists that I'm
on and I'd rather see a hard "Nope not supporting later Qt!" in the
packaging controls than not if there's no intention for this to support
future Qt)


Thomas

Hi Thomas!

qtchooser is perfectly co-installable with Qt 6 libraries, and I don't see why
we should disallow people to use qtchooser (for Qt 5) while also having Qt 6
installed.

Eventually qtchooser will be removed, but the majority of Qt software is still
using Qt 5 and not Qt 6, so it's still useful and it's very likely that users
will have both Qt 5 and Qt 6 installed.

Why do many qt6 packages have a dependency on qtchooser if you are not
supporting Qt6 with qtchooser?

   qt6-webengine-dev-tools
   qt6-l10n-tools
   qt6-documentation-tools
   qt6-declarative-dev-tools
   qt6-base-dev-tools
   qmlscene-qt6
   qml-qt6
   assistant-qt6
   linguist-qt6
   designer-qt6

I discussed this with my co-maintainers, and we decided to remove these
dependencies.