From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/
Date: Sun, 22 May 2022 06:37:47 +0000 (UTC) [thread overview]
Message-ID: <1653201417.d08d5f0dea3d8580c55a052d6424863d6aeb8ae9.juippis@gentoo> (raw)
commit: d08d5f0dea3d8580c55a052d6424863d6aeb8ae9
Author: Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 23 12:32:51 2022 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Sun May 22 06:36:57 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=d08d5f0d
general-concepts/dependencies: add new section for indirect deps
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
general-concepts/dependencies/text.xml | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index ef27ac2..ab1a799 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -781,6 +781,23 @@ There are three kinds of circular dependencies:
</li>
</ol>
+</body>
+</section>
+
+<section>
+<title>Indirect dependencies</title>
+<body>
+
+<p>
+Always list each direct dependency that your package needs to build and run
+correctly. Do not rely on dependency chains to meet the dependency
+requirements. For example, a package needs <c>dep1</c> and <c>dep2</c>, but
+<c>dep1</c> also depends on <c>dep2</c>. You might consider just adding
+<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>
+
</body>
</section>
</chapter>
next reply other threads:[~2022-05-22 6:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 6:37 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 19:36 [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/ Ulrich Müller
2023-09-27 8:30 Ulrich Müller
2022-06-24 9:14 Ulrich Müller
2022-05-27 9:00 Ulrich Müller
2022-05-22 6:37 Joonas Niilola
2022-02-21 5:22 Sam James
2022-02-21 5:22 Sam James
2021-10-19 9:27 Mike Frysinger
2021-10-13 13:42 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-23 7:47 Ulrich Müller
2019-12-21 5:19 Ulrich Müller
2019-10-16 18:49 Göktürk Yüksek
2018-09-10 15:20 Mike Gilbert
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2014-10-18 17:40 Markos Chandras
2013-07-29 21:53 Julian Ospald
2013-07-29 21:53 Julian Ospald
2011-02-17 21:08 Jeremy Olexa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1653201417.d08d5f0dea3d8580c55a052d6424863d6aeb8ae9.juippis@gentoo \
--to=juippis@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox