https://bugs.kde.org/show_bug.cgi?id=404484
--- Comment #5 from jm.ouwerk...@gmail.com --- Okay so with updated understanding on my part: - We do not want to edit metadata because we're not the only consumer - Instead we want some 'magic' in kdesrc-build which: 1. Should detect whether or not qt5 module set/submodules are *available* 2. Should detect whether or not they are (implicitly) required 3. Should then update the internal dependency state in kdesrc-build to include qt5/submodules - This logic should trigger only in specific circumstances. Exact trigger TBD. E.g. only when using `--include-dependencies`? Any specific "but omit these module" type switches that might conflict and should presumably take precedence? Also: maybe add a simple `--try-building-qt5` switch for testing during development while we figure out the exact trigger conditions here? -- You are receiving this mail because: You are watching all bug changes.
