From 1f4eb2b2cb996e95f5fb1f09ee912082c8957fea Mon Sep 17 00:00:00 2001 From: Andrei Horodniceanu Date: Thu, 26 Sep 2024 12:08:38 +0300 Subject: g-c/dependencies: Clarify the stance on circular dependencies MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Signed-off-by: Ulrich Müller --- general-concepts/dependencies/text.xml | 8 ++++++++ 1 file changed, 8 insertions(+) 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: +

+While circular dependencies should be avoided, an exception can be made for +test-only dependencies. Similar to the example above with the tests of +dev-python/setuptools, 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. +

+ -- cgit v1.2.3-65-gdbad