commit: 94057052e439ab6fe70cb0560211ce36d56ec2b8
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri May 27 08:59:21 2022 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri May 27 08:59:21 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=94057052
general-concepts/dependencies: Whitespace
Fixes: d08d5f0dea3d8580c55a052d6424863d6aeb8ae9
Fixes: 6c0b51ae63833c2ddfd58412727c0004db06d605
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
general-concepts/dependencies/text.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/general-concepts/dependencies/text.xml
b/general-concepts/dependencies/text.xml
index 59b1b37..0ff903d 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -631,7 +631,7 @@ package:
<dd>
Use a tool like <c>scanelf -n</c> (from app-misc/pax-utils) or
<c>objdump -p</c> (from sys-devel/binutils) to list <c>DT_NEEDED</c>
- entries.
+ entries.
app-portage/iwdevtools and portage's own <c>qa-unresolved-soname-deps</c>
<b>FEATURE</b> can help finding these.
</dd>
@@ -804,7 +804,7 @@ requirements. For example, a package needs <c>dep1</c> and
<c>dep2</c>, but
<c>dep1</c> since it currently pulls <c>dep2</c> too, but in the future,
<c>dep1</c> might drop <c>dep2</c> as a dependency, or make it conditional with
USE flags. This would then break building your ebuild.
-</p>
+</p>
</body>
</section>
