| 1 |
Portage doesn't treat things listed in USE_EXPAND as incremental, and |
| 2 |
nothing relies upon it behaving either way. Since that's the case, we |
| 3 |
don't really want USE_EXPAND_VALUES_* vars being special either. |
| 4 |
--- |
| 5 |
profile-variables.tex | 3 --- |
| 6 |
1 files changed, 0 insertions(+), 3 deletions(-) |
| 7 |
|
| 8 |
diff --git a/profile-variables.tex b/profile-variables.tex |
| 9 |
index 76623e3..9ac607e 100644 |
| 10 |
--- a/profile-variables.tex |
| 11 |
+++ b/profile-variables.tex |
| 12 |
@@ -18,7 +18,6 @@ variables must be treated in this fashion: |
| 13 |
\item \t{USE\_EXPAND\_HIDDEN} |
| 14 |
\item \t{CONFIG\_PROTECT} |
| 15 |
\item \t{CONFIG\_PROTECT\_MASK} |
| 16 |
-\item Any variable whose name is listed in \t{USE\_EXPAND} |
| 17 |
\end{compactitem} |
| 18 |
|
| 19 |
If the package manager supports any EAPI listed in table~\ref{tab:profile-iuse-injection-table} as |
| 20 |
@@ -28,8 +27,6 @@ incrementally; otherwise, the following variables may or may not be treated incr |
| 21 |
\item \t{IUSE\_IMPLICIT} |
| 22 |
\item \t{USE\_EXPAND\_IMPLICIT} |
| 23 |
\item \t{USE\_EXPAND\_UNPREFIXED} |
| 24 |
-\item Any variable whose name is \t{USE\_EXPAND\_VALUES\_\$\{value\}}, where \t{\$\{value\}} is any |
| 25 |
- value in \t{USE\_EXPAND\_IMPLICIT}. |
| 26 |
\end{compactitem} |
| 27 |
|
| 28 |
Other variables, except where they affect only package-manager-specific functionality (such as |
| 29 |
-- |
| 30 |
1.6.2 |
Archives