https://bugs.kde.org/show_bug.cgi?id=404484
--- Comment #4 from jm.ouwerk...@gmail.com ---
As I understand it now:
1.) There is a typo in the metadata Q instead q in qt5. This change is
necessary to make kdesrc-build sit up and take notice when including
qt5-build-include
2.) However if you do that and don't include qt5-build-include the qt5
dependency is likely to be visited multiple times with --include-dependencies
because everything *does* now depend on qt5.
- Speculation on my part here: because qt5 in that case does not resolve
to a valid module/set kdesrc-build will not mark it as going to be built, but
because it is depended upon multiple times now this means it trips the cycle
detection logic.
- Test case: can you construct a kdesrc-build command which includes two
KDE projects but specifically omits a shared dependency from the build. If the
theory holds, then the cycle detection logic should also trip in that case.
3.) Speculation on my part: kdesrc-build is silent about modules declared by
metadata which it cannot resolve through the include files to actual modules.
- Test case: inject a dummy does-not-exist module as dependency for
something.
If #2 holds we have a separate kdesrc-build bug on our hands here.
--
You are receiving this mail because:
You are watching all bug changes.
