| 1 |
Config arguably would benefit from env saving, but portage hasn't |
| 2 |
done it afaik, ever, so we can't really go retroactive on that one. |
| 3 |
--- |
| 4 |
ebuild-env-state.tex | 4 ++-- |
| 5 |
1 files changed, 2 insertions(+), 2 deletions(-) |
| 6 |
|
| 7 |
diff --git a/ebuild-env-state.tex b/ebuild-env-state.tex |
| 8 |
index 82bf6dc..7b764f5 100644 |
| 9 |
--- a/ebuild-env-state.tex |
| 10 |
+++ b/ebuild-env-state.tex |
| 11 |
@@ -5,8 +5,8 @@ Exported and default scope variables are saved between functions. A non-local va |
| 12 |
function earlier in the call sequence must have its value preserved for later functions, including |
| 13 |
functions executed as part of a later uninstall. |
| 14 |
|
| 15 |
-\note \t{pkg\_pretend} is \e{not} part of the normal call sequence, and does not take part in |
| 16 |
-environment saving. |
| 17 |
+\note \t{pkg\_pretend}, \t{pkg\_info}, \t{pkg\_config} are \e{not} part of the normal call sequence, |
| 18 |
+thus do not take part in environment saving. |
| 19 |
|
| 20 |
Variables that were exported must remain exported in later functions; variables with default |
| 21 |
visibility may retain default visibility or be exported. |
| 22 |
-- |
| 23 |
1.7.6 |
Archives