[gentoo-pms] [PATCH] ebuild-env-vars: Require DISTDIR & FILESDIR to be consistent

[Michał Górny]

Require both DISTDIR and FILESDIR variables to have consistent value
across phases. We need to guarantee that the value used in global scope
to propagate PATCHES array will be still valid in src_prepare().
Furthermore, as Ulrich Müller points out that PMS requires ebuilds to
recalculate any value derived from inconsistent variables, therefore
colliding with the global-scope assignment.
---
 ebuild-env-vars.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
index 6b74d90..262bcf9 100644
--- a/ebuild-env-vars.tex
+++ b/ebuild-env-vars.tex
@@ -86,14 +86,14 @@ variable.
 \t{FILESDIR} &
     \t{src\_*}, global~scope\footnote{Not necessarily present when installing from a binary package.
     Ebuilds must not access the directory in global scope.} &
-    No &
+    Yes &
     The full path to a directory where the files from the package's files directory (used for
     small support files or patches) are available. See section~\ref{sec:package-dirs}. May or may
     not exist; if a repository provides no support files for the package in question then an ebuild
     must be prepared for the situation where \t{FILESDIR} points to a non-existent directory. \\
 \t{DISTDIR} &
     Ditto &
-    No &
+    Yes &
     The full path to the directory in which the files in the \t{A} variable are stored. \\
 \t{PORTDIR} &
     \t{src\_*} &
-- 
2.12.0