[sdk/kde-builder] kde_builder_lib: chore: Remove a todo comment for sort failed by explicitly selected
Andrew Shark <[email protected]>
| Newsgroups | gmane.comp.kde.cvs |
|---|---|
| Message-ID | <[email protected]> |
Git commit e5c2d74930d5d2fb8300fcdb93af2f75a899dbcd by Andrew Shark.
Committed on 03/08/2026 at 15:30.
Pushed by ashark into branch 'master'.
chore: Remove a todo comment for sort failed by explicitly selected
There is no benefit of this, since every module should be
there as a dependency of some kind when selectors are in play.
See https://invent.kde.org/sdk/kde-builder/-/merge_requests/122
M +0 -7 kde_builder_lib/debug_order_hints.py
https://invent.kde.org/sdk/kde-builder/-/commit/e5c2d74930d5d2fb8300fcdb93af2f75a899dbcd
diff --git a/kde_builder_lib/debug_order_hints.py b/kde_builder_lib/debug_order_hints.py
index d713e5bf..935c187c 100644
--- a/kde_builder_lib/debug_order_hints.py
+++ b/kde_builder_lib/debug_order_hints.py
@@ -81,13 +81,6 @@ class DebugOrderHints:
if order:
return order
- # TODO we could tag explicitly selected modules from command line?
- # If we do so, then the user is probably more interested in debugging
- # those first, rather than "unrelated" noise from modules pulled in due
- # to possibly overly broad dependency declarations. In that case we
- # should sort explicitly tagged modules next highest, after dependency
- # ordering.
-
# Assuming no dependency resolution, next favour possible root causes as
# may be inferred from the dependency tree.
#