[gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/

public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed

From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/
Date: Mon, 25 May 2020 15:43:27 +0000 (UTC)	[thread overview]
Message-ID: <1589022379.be93eaeb521f18b0f8b563accd1d2b398bb87b02.ulm@gentoo> (raw)

commit:     be93eaeb521f18b0f8b563accd1d2b398bb87b02
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 15 18:23:47 2020 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat May  9 11:06:19 2020 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=be93eaeb

general-concepts/dependencies: Better section structure.

Collect similar topics as subsections under new section headers.

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 general-concepts/dependencies/text.xml | 114 +++++++++++++++++----------------
 1 file changed, 60 insertions(+), 54 deletions(-)

diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index 1a1d970..52d053e 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -2,16 +2,19 @@
 <guide self="general-concepts/dependencies/">
 <chapter>
 <title>Dependencies</title>
-
 <body>
 
 <p>
 Automatic dependency resolution is one of the most useful features
 provided by <c>emerge</c>.
 </p>
+
 </body>
 
 <section>
+<title>Dependency types</title>
+
+<subsection>
 <title>CHOST vs CBUILD</title>
 <body>
 
@@ -41,9 +44,9 @@ of dependencies are merged.
 </p>
 
 </body>
-</section>
+</subsection>
 
-<section>
+<subsection>
 <title>Build Dependencies</title>
 <body>
 
@@ -67,9 +70,9 @@ In earlier EAPIs, all build dependencies are placed in <c>DEPEND</c>.
 </p>
 
 </body>
-</section>
+</subsection>
 
-<section>
+<subsection>
 <title>Runtime Dependencies</title>
 <body>
 
@@ -91,9 +94,9 @@ Items which are in <c>RDEPEND</c> but not <c>DEPEND</c> could <e>in theory</e> b
 </p>
 
 </body>
-</section>
+</subsection>
 
-<section>
+<subsection>
 <title>Post Dependencies</title>
 <body>
 
@@ -105,39 +108,13 @@ while in general case <c>RDEPEND</c> should be used instead.
 </p>
 
 </body>
+</subsection>
 </section>
 
 <section>
-<title>Implicit System Dependency</title>
-<body>
+<title>Dependency Syntax</title>
 
-<p>
-All packages have an implicit compile-time and runtime dependency upon the
-entire <c>@system</c> set. It is therefore not necessary, nor
-advisable, to
-specify dependencies upon toolchain packages like <c>gcc</c>, <c>libc</c> and
-so on, except where specific versions or packages (for example, <c>glibc</c>
-over <c>uclibc</c>) are required.  Note that this rule also needs consideration
-for packages like <c>flex</c>, <c>zlib</c> and <c>libtool</c>, which aren't in
-the <c>@system</c> set for every profile. For example, the embedded
-profile doesn't have <c>zlib</c> in <c>@system</c>, the <c>libtool</c>
-ABI might
-change and break building order and <c>flex</c> might get removed from the
-<c>@system</c> set in future.
-</p>
-
-<p>
-However, packages which are included in the <c>@system</c> set, or are
-dependencies of <c>@system</c> set packages, should generally include
-a complete dependency list (excluding bootstrap packages). This makes
-<c>emerge -e @system</c>
-possible when installing from a stage 1 or stage 2 tarball.
-</p>
-
-</body>
-</section>
-
-<section>
+<subsection>
 <title>Basic Dependency Syntax</title>
 <body>
 
@@ -159,9 +136,9 @@ When specifying names, the category part should be treated as mandatory.
 </p>
 
 </body>
-</section>
+</subsection>
 
-<section>
+<subsection>
 <title>Version Dependencies</title>
 <body>
 
@@ -179,7 +156,7 @@ This states that at least version 0.9.7d of <c>openssl</c> is required.
 </p>
 </body>
 
-<subsection>
+<subsubsection>
 <title>Version Specifiers</title>
 <body>
 
@@ -222,9 +199,9 @@ Available version specifiers are:
 </table>
 
 </body>
-</subsection>
+</subsubsection>
 
-<subsection>
+<subsubsection>
 <title>Ranged Dependencies</title>
 <body>
 
@@ -244,9 +221,9 @@ asterisk. Also note that when selecting all versions in a specific
 </p>
 
 </body>
-</subsection>
+</subsubsection>
 
-<subsection>
+<subsubsection>
 <title>Blockers</title>
 <body>
 
@@ -343,10 +320,10 @@ newer package that caused the issues.
 </p>
 
 </body>
+</subsubsection>
 </subsection>
-</section>
 
-<section>
+<subsection>
 <title>SLOT Dependencies</title>
 <body>
 
@@ -370,7 +347,7 @@ DEPEND="qt3? ( ~x11-libs/qt-3.3.8:3 )
 </codesample>
 </body>
 
-<subsection>
+<subsubsection>
 <title>Slot Operators</title>
 <body>
 
@@ -407,10 +384,10 @@ RDEPEND="media-libs/cogl:1.0=
 </codesample>
 
 </body>
+</subsubsection>
 </subsection>
-</section>
 
-<section>
+<subsection>
 <title>USE-Conditional Dependencies</title>
 <body>
 
@@ -464,9 +441,9 @@ DEPEND="!build? (
 </codesample>
 
 </body>
-</section>
+</subsection>
 
-<section>
+<subsection>
 <title>Any of Many Dependencies</title>
 <body>
 
@@ -487,7 +464,7 @@ DEPEND="baz? ( || ( app-misc/foo app-misc/bar ) )"
 </codesample>
 </body>
 
-<subsection>
+<subsubsection>
 <title>Any of Many Versus USE</title>
 <body>
 
@@ -509,10 +486,10 @@ flag is not necessary if and only if all of the following hold:
 </ul>
 
 </body>
+</subsubsection>
 </subsection>
-</section>
 
-<section>
+<subsection>
 <title>Built with USE Dependencies</title>
 <body>
 
@@ -567,7 +544,7 @@ There are also shortcuts for conditional situations:
 </table>
 </body>
 
-<subsection>
+<subsubsection>
 <title>Use dependency defaults</title>
 <body>
 
@@ -592,9 +569,38 @@ DEPEND="
 </codesample>
 
 </body>
+</subsubsection>
 </subsection>
 </section>
 
+<section>
+<title>Implicit System Dependency</title>
+<body>
+
+<p>
+All packages have an implicit compile-time and runtime dependency upon the
+entire <c>@system</c> set. It is therefore not necessary, nor advisable, to
+specify dependencies upon toolchain packages like <c>gcc</c>, <c>libc</c> and
+so on, except where specific versions or packages (for example, <c>glibc</c>
+over <c>uclibc</c>) are required. Note that this rule also needs consideration
+for packages like <c>flex</c>, <c>zlib</c> and <c>libtool</c>, which aren't in
+the <c>@system</c> set for every profile. For example, the embedded profile
+doesn't have <c>zlib</c> in <c>@system</c>, the <c>libtool</c> ABI might
+change and break building order and <c>flex</c> might get removed from the
+<c>@system</c> set in future.
+</p>
+
+<p>
+However, packages which are included in the <c>@system</c> set, or are
+dependencies of <c>@system</c> set packages, should generally include
+a complete dependency list (excluding bootstrap packages). This makes
+<c>emerge -e @system</c> possible when installing from a stage 1 or stage 2
+tarball.
+</p>
+
+</body>
+</section>
+
 <section>
 <title>Test Dependencies</title>
 <body>

next             reply	other threads:[~2020-05-25 15:43 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 15:43 Ulrich Müller [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-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-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

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:1a1d970 dfblob:52d053e )
 OR (
bs:"[gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/" )
	(help)

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=1589022379.be93eaeb521f18b0f8b563accd1d2b398bb87b02.ulm@gentoo \
    --to=ulm@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