https://bugs.kde.org/show_bug.cgi?id=404484
--- Comment #3 from Michael Pyne <mp...@kde.org> --- It's both metadata and logic, to some extent. Qt5 is inherently a base dependency in the metadata itself, which kdesrc-build ignores and filters out because (at that time) Qt5 was meant to be provided by the base system. I'm really not sure I want to add "all of Qt5" as a mandatory kdesrc-build dependency, though there may be no other easier way to bootstrap the initial setup / "first run" process. But in your case you specifically add qt5-build-include and the script still aborts. This case should be made to work no matter what. I suspect that kdesrc-build is including qt5 in the build list, but not recognizing that qt5 will eventually come up with the missing qmake during the build. The check that fails here is made very early in the run to allow the user to fix without wasting an hour first on a 100+ failed git repo builds. In fact I think you may have already fixed this in your other commit to add Qt's paths to the search for essential build programs. I would avoid adding qt5 as a dependency as you're tracking in D19171 because that is meant for things that *have* to be built by kdesrc-build and/or build.kde.org, and I want to continue to support users who either build their own Qt 5 or use system packages. I'll comment there as well. -- You are receiving this mail because: You are watching all bug changes.
