aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrei Horodniceanu <a.horodniceanu@proton.me>2024-09-26 12:08:38 +0300
committerUlrich Müller <ulm@gentoo.org>2024-09-28 21:36:07 +0200
commit1f4eb2b2cb996e95f5fb1f09ee912082c8957fea (patch)
tree8bcf5163cd2e1fba7f8fcf7cb696bd960037bb1f
parentebuild-writing/error-handling: Refer to PIPESTATUS, not its value (diff)
downloaddevmanual-master.tar.gz
devmanual-master.tar.bz2
devmanual-master.zip
g-c/dependencies: Clarify the stance on circular dependenciesHEADmaster
I had a package that needed changes that would introduce a dependency cycle with USE=test and I had to ask on IRC whether this was OK. Sam told me not to worry about it and recommended that the devmanual should note this. So, add a paragraph that discourages dependency cycles but expresses that cycles provoked by USE=test can usually be ignored. Signed-off-by: Andrei Horodniceanu <a.horodniceanu@proton.me> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
-rw-r--r--general-concepts/dependencies/text.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index 6c3207d..407e4c4 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -821,6 +821,14 @@ There are three kinds of circular dependencies:
</li>
</ol>
+<p>
+While circular dependencies should be avoided, an exception can be made for
+test-only dependencies. Similar to the example above with the tests of
+<c>dev-python/setuptools</c>, if a package needs itself, directly or
+indirectly, in order to run its tests, it is usually fine to leave it
+as-is. You should fix it if you can but don't go to extensive lengths for it.
+</p>
+
</body>
</section>