diff options
| author |   Göktürk Yüksek <gokturk@binghamton.edu> | 2016-05-04 04:53:44 -0400 |
|---|---|---|
| committer | Göktürk Yüksek <gokturk@binghamton.edu> | 2016-05-04 05:08:20 -0400 |
| commit | 658d52f0eafaa6c139aa1c6ba5c249afa2e2f4e1 (patch) | |
| tree | 40e41e995df5495445da35ea8a605f5769883d03 /appendices/common-problems | |
| parent | ebuild-writing/variables: add HOME to the list of read-only variables (diff) | |
| download | devmanual-658d52f0eafaa6c139aa1c6ba5c249afa2e2f4e1.tar.gz devmanual-658d52f0eafaa6c139aa1c6ba5c249afa2e2f4e1.tar.bz2 devmanual-658d52f0eafaa6c139aa1c6ba5c249afa2e2f4e1.zip | |
appendices/common-problems: remove the misleading sandbox violation example
In the "Handling Access Violations" section, there is an example of a
build system causing a sandbox violation by attempting to access
HOME. Per PMS, HOME is a predefined read-only environment variable
that points to a temporary location, which doesn't cause any sandbox
violations. Remove the example while keeping the idea of tricking the
build system into using a safer location.
Signed-off-by: Göktürk Yüksek <gokturk@binghamton.edu>
Diffstat (limited to 'appendices/common-problems')
| -rw-r--r-- | appendices/common-problems/text.xml | 30 |
1 files changed, 5 insertions, 25 deletions
diff --git a/appendices/common-problems/text.xml b/appendices/common-problems/text.xml index b0a7e58..2a9a2e7 100644 --- a/appendices/common-problems/text.xml +++ b/appendices/common-problems/text.xml @@ -214,31 +214,11 @@ ebuilds. </p> <p> -Access violations most commonly occur during the install phase. See -<c>src_install</c> and <uri link="::general-concepts/install-destinations/"/> -for discussion. -</p> - -<p> -Sometimes problems can also occur with packages attempting to write to -<c>${HOME}</c>. To get around this, it is usually sufficient to trick the build -system into using a safer location. For example, the <c>fluxbox</c> menu generator -tries to work in <c>${HOME}/.fluxbox</c> <d/> to get around this, the following is -used: -</p> - -<codesample lang="ebuild"> -ebegin "Creating a menu file (may take a while)" -mkdir -p "${T}/home/.fluxbox" || die "mkdir home failed" -MENUFILENAME="${S}/data/menu" MENUTITLE="Fluxbox ${PV}" \ - CHECKINIT="no. go away." HOME="${T}/home" \ - "${S}"/util/fluxbox-generate_menu -is -ds \ - || die "menu generation failed" -eend $? -</codesample> - -<p> -In this situation, providing a fake home directory is all that is needed. +Access violations most commonly occur during the install +phase. Sometimes it is possible to get around the sandbox violations +by tricking the build system into using a safer location. See +<c>src_install</c> and +<uri link="::general-concepts/install-destinations/"/> for discussion. </p> </body> |