I think it's time to change the default version of qt used by the system from 4 to 5. This bug purpose is to track the process Reproducible: Always
We should probably switch to Qt5 soonish. Qt4 is slowly being removed from the tree. On qt4 free system running qmake just prints qmake: could not find a Qt installation of '' Of course qmake -qt5 still works.
(In reply to Andrius Štikonas from comment #1) > We should probably switch to Qt5 soonish. Second that, imo all the important bugs are fixed.
Agreed, we can do the switch in 5.9.4. Or should we wait for 5.10.x? Note that currently the symlink is statically created in qt4-build-multilib.eclass, therefore we need to revbump qtcore:4 as well, and add appropriate blockers to qtcore:5.
Hm, yes, let's do that with 5.9.4 - why wait. :) USE=qt4 was already dropped from desktop profile with a few individual exceptions, and revdeps are being phased out at a fast pace.
(In reply to Davide Pesavento from comment #3) > Note that currently the symlink is statically created in > qt4-build-multilib.eclass, therefore we need to revbump qtcore:4 as well, > and add appropriate blockers to qtcore:5. Should we just revbump-by-git-mv all current qtcore versions at once to enforce the eclass changes? Otherwise we'd have to put the link creation behind conditionals and somehow I don't think we need another qtcore:4 stabilisation.
(In reply to Andreas Sturmlechner from comment #5) > (In reply to Davide Pesavento from comment #3) > > Note that currently the symlink is statically created in > > qt4-build-multilib.eclass, therefore we need to revbump qtcore:4 as well, > > and add appropriate blockers to qtcore:5. > > Should we just revbump-by-git-mv all current qtcore versions at once to > enforce the eclass changes? Otherwise we'd have to put the link creation > behind conditionals and somehow I don't think we need another qtcore:4 > stabilisation. I'm not following. Simply revbumping isn't enough to prevent the file collision.
Yes, including adding the necessary blocker. I was just getting confused by 'do the switch with 5.9.4' when we need to bump and add the block in all qtcore:* ebuilds.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0b94bf7676964f887842ca524d90821ad64dca9e commit 0b94bf7676964f887842ca524d90821ad64dca9e Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-02-14 23:58:55 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-02-22 19:15:45 +0000 dev-qt/qtcore: Revbumps to enforce qtchooser qt5-default Follow-up to a888955 and 5d7ff88 Bug: https://bugs.gentoo.org/564622 Package-Manager: Portage-2.3.24, Repoman-2.3.6 dev-qt/qtcore/{qtcore-4.8.7-r3.ebuild => qtcore-4.8.7-r4.ebuild} | 0 dev-qt/qtcore/{qtcore-5.7.1-r3.ebuild => qtcore-5.7.1-r4.ebuild} | 6 ++++-- dev-qt/qtcore/{qtcore-5.9.4-r1.ebuild => qtcore-5.9.4-r2.ebuild} | 4 +++- 3 files changed, 7 insertions(+), 3 deletions(-) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e934cae4d291f0c1d084ab12bbccd0eadb6f0341 commit e934cae4d291f0c1d084ab12bbccd0eadb6f0341 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-02-14 22:46:27 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-02-22 19:15:45 +0000 qt5-build.eclass: Set qtchooser default.conf link to qt5.conf Bug: https://bugs.gentoo.org/564622 eclass/qt5-build.eclass | 2 ++ 1 file changed, 2 insertions(+) https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5bff32cf9143ec0526913e80114dc8dd500f5e07 commit 5bff32cf9143ec0526913e80114dc8dd500f5e07 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-02-14 22:45:09 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-02-22 19:15:45 +0000 qt4-build-multilib.eclass: Remove qtchooser default.conf link Bug: https://bugs.gentoo.org/564622 eclass/qt4-build-multilib.eclass | 2 -- 1 file changed, 2 deletions(-)}
I guess we are done here.
I am trying to develop against Qt4 and a simple `find_package(Qt4 REQUIRED)` now fails: epsft-53 cmake-testing $ cat CMakeLists.txt cmake_minimum_required(VERSION 3.6.0) project(TESTING CXX) find_package(Qt4 4.8 REQUIRED) message(STATUS "QT4_FOUND = ${QT4_FOUND}") epsft-53 cmake-testing $ cmake . CMake Error at /usr/share/cmake/Modules/FindQt4.cmake:1330 (message): Found unsuitable Qt version "5.9.4" from /usr/bin/qmake, this code requires Qt 4.x Call Stack (most recent call first): CMakeLists.txt:5 (find_package) -- Configuring incomplete, errors occurred! See also "/tmp/cmake-testing/CMakeFiles/CMakeOutput.log". epsft-53 cmake-testing $ qlist -ICv dev-qt dev-qt/linguist-tools-5.9.4 dev-qt/qt3support-4.8.7 dev-qt/qtchooser-0_p20170803 dev-qt/qtconcurrent-5.9.4 dev-qt/qtcore-4.8.7-r4 dev-qt/qtcore-5.9.4-r2 dev-qt/qtdbus-5.9.4 dev-qt/qtdeclarative-4.8.7 dev-qt/qtdeclarative-5.9.4 dev-qt/qtgui-4.8.7 dev-qt/qtgui-5.9.4-r3 dev-qt/qtnetwork-5.9.4 dev-qt/qtopengl-4.8.7 dev-qt/qtopengl-5.9.4 dev-qt/qtprintsupport-5.9.4 dev-qt/qtscript-4.8.7 dev-qt/qtscript-5.9.4 dev-qt/qtsql-4.8.7-r1 dev-qt/qtsvg-4.8.7 dev-qt/qtsvg-5.9.4-r1 dev-qt/qttest-5.9.4 dev-qt/qttranslations-4.8.7 dev-qt/qtwebchannel-5.9.4 dev-qt/qtwebengine-5.9.4 dev-qt/qtwebkit-4.10.4 dev-qt/qtwidgets-5.9.4-r1 dev-qt/qtx11extras-5.9.4 dev-qt/qtxml-5.9.4 dev-qt/qtxmlpatterns-4.8.7 dev-qt/qtxmlpatterns-5.9.4
Quote from FindQt4.cmake from CMake: > Finding and Using Qt4 > ^^^^^^^^^^^^^^^^^^^^^ > This module can be used to find Qt4. The most important issue is that > the Qt4 qmake is available via the system path. This qmake is then > used to detect basically everything else. This module defines a > number of :prop_tgt:`IMPORTED` targets, macros and variables.
Please open a new bug.