| 1 |
On śro, 2017-05-03 at 19:51 +0200, Ulrich Müller wrote: |
| 2 |
> The restriction for PM special variables applies to the preceding |
| 3 |
> sentence. |
| 4 |
|
| 5 |
Are you sure about this? I thought it was meant to apply to the whole |
| 6 |
section. |
| 7 |
|
| 8 |
> --- |
| 9 |
> ebuild-env-state.tex | 5 ++--- |
| 10 |
> 1 file changed, 2 insertions(+), 3 deletions(-) |
| 11 |
> |
| 12 |
> diff --git a/ebuild-env-state.tex b/ebuild-env-state.tex |
| 13 |
> index 70a0e46..d2cf7b4 100644 |
| 14 |
> --- a/ebuild-env-state.tex |
| 15 |
> +++ b/ebuild-env-state.tex |
| 16 |
> @@ -9,9 +9,8 @@ functions executed as part of a later uninstall. |
| 17 |
> environment saving. |
| 18 |
> |
| 19 |
> Variables that were exported must remain exported in later functions; variables with default |
| 20 |
> -visibility may retain default visibility or be exported. |
| 21 |
> - |
| 22 |
> -Variables with special meanings to the package manager are excluded from this rule. |
| 23 |
> +visibility may retain default visibility or be exported. Variables with special meanings to the |
| 24 |
> +package manager are excluded from this rule. |
| 25 |
> |
| 26 |
> Global variables must only contain invariant values (see~\ref{sec:metadata-invariance}). If a global |
| 27 |
> variable's value is invariant, it may have the value that would be generated at any given point |
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Michał Górny |
Archives