commit: e39511f0353770fdc4b7e4ce45b7ff0ed034b6d8
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 25 18:38:51 2020 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Jul 5 19:03:44 2020 +0000
URL: https://gitweb.gentoo.org/proj/pms.git/commit/?id=e39511f0
ebuild-functions.tex: Phase functions can write to temporary dirs.
All package managers support that functions like pkg_pretend() write
to temporary directories T, TMPDIR and HOME. This is also used in the
tree, see for example bug 469210. Update the spec to match this.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-functions.tex | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/ebuild-functions.tex b/ebuild-functions.tex
index 4a13db6..3935800 100644
--- a/ebuild-functions.tex
+++ b/ebuild-functions.tex
@@ -6,11 +6,12 @@
The following is a list of functions that an ebuild, or eclass, may define,
and which will be called
by the package manager as part of the build and/or install process. In all
cases the package manager
must provide a default implementation of these functions; unless otherwise
stated this must be a
-no-op. Most functions must assume only that they have write access to the
package's working
-directory (the \t{WORKDIR} environment variable; see
section~\ref{sec:ebuild-env-vars}), and the
-temporary directory \t{T}; exceptions are noted below. All functions may
assume that they have read
-access to all system libraries, binaries and configuration files that are
accessible to normal
-users.
+no-op. All functions may assume that they have read access to all system
libraries, binaries and
+configuration files that are accessible to normal users, as well as write
access to the temporary
+directories specified by the \t{T}, \t{TMPDIR} and \t{HOME} environment
variables
+(see section~\ref{sec:ebuild-env-vars}). Most functions must assume only that
they have additional
+write access to the package's working directory (the \t{WORKDIR} environment
variable); exceptions
+are noted below.
The environment for functions run outside of the build sequence (that is,
\t{pkg_config},
\t{pkg_info}, \t{pkg_prerm} and \t{pkg_postrm}) must be the environment used
for the build of the
