1 |
>>>>> On Sun, 5 Dec 2010, Ciaran McCreesh wrote: |
2 |
|
3 |
>> >> - Calling pkg_pretend. |
4 |
|
5 |
> pkg_pretend's sandboxed and isn't supposed to be modifying /, so |
6 |
> that should be ok. |
7 |
|
8 |
Then pkg_pretend should be mentioned as a further exception (unless we |
9 |
decide that the whole section should be removed): |
10 |
|
11 |
--- ebuild-env-invariancy.tex~ |
12 |
+++ ebuild-env-invariancy.tex |
13 |
@@ -7,8 +7,8 @@ |
14 |
\item Variancy is any package manager action that modifies either |
15 |
\t{ROOT} or \t{/} in any way that isn't merely a simple addition of |
16 |
something that doesn't alter other packages. This includes any |
17 |
- non-default call to any \t{pkg} phase function except \t{pkg\_setup}, |
18 |
- a merge of any package or an unmerge of any package. |
19 |
+ non-default call to any \t{pkg} phase function except \t{pkg\_pretend} |
20 |
+ and \t{pkg\_setup}, a merge of any package or an unmerge of any package. |
21 |
\item As an exception, changes to \t{DISTDIR} do not count as variancy. |
22 |
\item The \t{pkg\_setup} function may be assumed not to introduce variancy. |
23 |
Thus, ebuilds must not perform variant actions in this phase. |