aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGöktürk Yüksek <gokturk@gentoo.org>2016-08-29 13:58:03 -0400
committerGöktürk Yüksek <gokturk@gentoo.org>2016-08-29 13:58:03 -0400
commitb6eb727944e8fffc8c9b9e2ee97944007a3cc850 (patch)
tree4188fedd8ba295ab70f2d04cae004bf307303e9f
parentebuild-maintenance: <warning/> rather than <warn/>. (diff)
downloaddevmanual-b6eb7279.tar.gz
devmanual-b6eb7279.tar.bz2
devmanual-b6eb7279.zip
ebuild-writing/users-and-groups: clarify the language wrt sandbox in pkg_setup.
pkg_setup is not sandbox safe, it's sandbox-disabled. Reported-By: David Seifert <soap@gentoo.org>
-rw-r--r--ebuild-writing/users-and-groups/text.xml6
1 files changed, 4 insertions, 2 deletions
diff --git a/ebuild-writing/users-and-groups/text.xml b/ebuild-writing/users-and-groups/text.xml
index 5030318..e1d0fcd 100644
--- a/ebuild-writing/users-and-groups/text.xml
+++ b/ebuild-writing/users-and-groups/text.xml
@@ -8,8 +8,10 @@
If your ebuild requires a user or group to be added for a daemon, for example,
this should be performed via the functions available in <c>user.eclass</c>.
Regardless of whether you are adding a group or a user, this should be performed
-in the <c>pkg_setup</c> function: <c>pkg_setup</c> is sandbox-safe,
-is called before the compile process so a build that requires the user to exist will
+in the <c>pkg_setup</c> phase function. <c>pkg_setup</c> is called
+before the compile process, with
+<uri link="::general-concepts/sandbox">sandbox</uri>
+disabled, so a build that requires the user to exist will
have it, and is also called for both binary and source packages. You may also
use the <c>pkg_preinst</c> or <c>pkg_postinst</c> functions for user creation, if
the user is not required during or before <c>src_install</c>.