| 1 |
In effect, this means it's illegal to call use in global scope for EAPI |
| 2 |
3, and undefined otherwise. |
| 3 |
--- |
| 4 |
ebuild-env-vars.tex | 3 +++ |
| 5 |
1 files changed, 3 insertions(+), 0 deletions(-) |
| 6 |
|
| 7 |
diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex |
| 8 |
index a1713d2..e093218 100644 |
| 9 |
--- a/ebuild-env-vars.tex |
| 10 |
+++ b/ebuild-env-vars.tex |
| 11 |
@@ -245,6 +245,9 @@ This section discusses the handling of four variables: |
| 12 |
\item[USE] is a variable calculated by the package manager and exported to the ebuild environment. |
| 13 |
\end{description} |
| 14 |
|
| 15 |
+In all cases, the values of \t{IUSE\_REFERENCEABLE} and \t{IUSE\_EFFECTIVE} are undefined during |
| 16 |
+metadata generation. |
| 17 |
+ |
| 18 |
For EAPIs listed in table~\ref{tab:profile-iuse-injection-table} as not supporting profile defined |
| 19 |
\t{IUSE} injection, \t{IUSE\_REFERENCEABLE} is equal to the calculated \t{IUSE} value. For EAPIs |
| 20 |
where profile defined \t{IUSE} injection is supported, \t{IUSE\_REFERENCEABLE} is equal to |
| 21 |
-- |
| 22 |
1.6.2 |
Archives