Gentoo Archives: gentoo-pms

From: Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>
To: gentoo-pms@l.g.o
Cc: Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>
Subject: [gentoo-pms] [PATCH] Clarify RDEPEND=DEPEND wording
Date: Wed, 22 Jun 2011 20:04:55
As worded, it could be taken to imply that ebuilds could grep RDEPEND in
a phase function and expect DEPEND-specified values (and possibly not
eclass-specified values) to appear in there.  This goes against the
general rules for globally specified variables.
 ebuild-vars.tex |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/ebuild-vars.tex b/ebuild-vars.tex
index d183305..d971234 100644
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@ -129,11 +129,13 @@ ideally, an error in one ebuild should not prevent operations upon other ebuilds
 \featurelabel{rdepend-depend} In EAPIs listed in table~\ref{tab:rdepend-depend-table} as having
 \t{RDEPEND=DEPEND}, if \t{RDEPEND} is unset (but not if it is set to an empty string) in an ebuild,
-the package manager must set its value to be equal to the value of \t{DEPEND}.
+when generating metadata the package manager must treat its value as being equal to the value of
 When dealing with eclasses, only values set in the ebuild itself are considered for this behaviour;
 any \t{DEPEND} or \t{RDEPEND} set in an eclass does not change the implicit \t{RDEPEND=DEPEND} for
-the ebuild portion, and any \t{DEPEND} value set in an eclass does not get added to \t{RDEPEND}.
+the ebuild portion, and any \t{DEPEND} value set in an eclass does not get treated as being part of
 \begin{centertable}{EAPIs with \t{RDEPEND=DEPEND} Default} \label{tab:rdepend-depend-table}
     \begin{tabular}{ l l }