commit:     be7ec7f3d2965719ffb69879bd879fc9b48c6dc1
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 29 08:03:11 2019 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Jan 29 07:58:26 2020 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=be7ec7f3

general-concepts/dependencies: Improve PDEPEND

Rewrite the PDEPEND description to be more focused on its purpose.
Rename to 'Post Dependencies' to match PMS. Reverse the weird backwards
logic that indicated that they might be installed before the package
into saying that they may be installed after it. Clearly indicate
that its only purpose is to resolve circular dependencies.

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 general-concepts/dependencies/text.xml | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/general-concepts/dependencies/text.xml 
b/general-concepts/dependencies/text.xml
index 8deca1f..dde6cda 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -94,16 +94,14 @@ Items which are in <c>RDEPEND</c> but not <c>DEPEND</c> 
could <e>in theory</e> b
 </section>
 
 <section>
-<title>Post-Merge Dependencies</title>
+<title>Post Dependencies</title>
 <body>
 
 <p>
-The <c>PDEPEND</c> variable specifies dependencies that should be
-merged <e>after</e> the package, but which may be merged at any time,
-if the former is not possible. This is sometimes used for plugins
-that have a dependency upon the package being merged. Generally
-<c>PDEPEND</c> should be avoided in favour of <c>RDEPEND</c> except
-where this will create circular dependency chains.
+The <c>PDEPEND</c> variable specifies runtime dependencies that do not strictly
+require being satisfied immediately. They can be merged <e>after</e>
+the package. This variable is used purely to resolve circular dependencies,
+while in general case <c>RDEPEND</c> should be used instead.
 </p>
 
 </body>

Reply via email to