Config arguably would benefit from env saving, but portage hasn't
done it afaik, ever, so we can't really go retroactive on that one.
---
 ebuild-env-state.tex |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/ebuild-env-state.tex b/ebuild-env-state.tex
index 82bf6dc..7b764f5 100644
--- a/ebuild-env-state.tex
+++ b/ebuild-env-state.tex
@@ -5,8 +5,8 @@ Exported and default scope variables are saved between functions. A non-local va
 function earlier in the call sequence must have its value preserved for later functions, including
 functions executed as part of a later uninstall.
 
-\note \t{pkg\_pretend} is \e{not} part of the normal call sequence, and does not take part in
-environment saving.
+\note \t{pkg\_pretend}, \t{pkg\_info}, \t{pkg\_config} are \e{not} part of the normal call sequence,
+thus do not take part in environment saving.
 
 Variables that were exported must remain exported in later functions; variables with default
 visibility may retain default visibility or be exported.
-- 
1.7.6