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
1 As worded, it could be taken to imply that ebuilds could grep RDEPEND in
2 a phase function and expect DEPEND-specified values (and possibly not
3 eclass-specified values) to appear in there. This goes against the
4 general rules for globally specified variables.
5 ---
6 ebuild-vars.tex | 6 ++++--
7 1 files changed, 4 insertions(+), 2 deletions(-)
9 diff --git a/ebuild-vars.tex b/ebuild-vars.tex
10 index d183305..d971234 100644
11 --- a/ebuild-vars.tex
12 +++ b/ebuild-vars.tex
13 @@ -129,11 +129,13 @@ ideally, an error in one ebuild should not prevent operations upon other ebuilds
15 \featurelabel{rdepend-depend} In EAPIs listed in table~\ref{tab:rdepend-depend-table} as having
16 \t{RDEPEND=DEPEND}, if \t{RDEPEND} is unset (but not if it is set to an empty string) in an ebuild,
17 -the package manager must set its value to be equal to the value of \t{DEPEND}.
18 +when generating metadata the package manager must treat its value as being equal to the value of
19 +\t{DEPEND}.
21 When dealing with eclasses, only values set in the ebuild itself are considered for this behaviour;
22 any \t{DEPEND} or \t{RDEPEND} set in an eclass does not change the implicit \t{RDEPEND=DEPEND} for
23 -the ebuild portion, and any \t{DEPEND} value set in an eclass does not get added to \t{RDEPEND}.
24 +the ebuild portion, and any \t{DEPEND} value set in an eclass does not get treated as being part of
25 +\t{RDEPEND}.
27 \begin{centertable}{EAPIs with \t{RDEPEND=DEPEND} Default} \label{tab:rdepend-depend-table}
28 \begin{tabular}{ l l }
29 --