Gentoo Archives: gentoo-pms

From: "Ulrich Müller" <ulm@g.o>
To: gentoo-pms@l.g.o
Subject: [gentoo-pms] Re: [PATCH] WORKDIR has same scope as FILESDIR and DISTDIR.
Date: Sat, 18 Mar 2017 15:04:32
Message-Id: 22733.19554.521284.942536@a1i15.kph.uni-mainz.de
In Reply to: [gentoo-pms] [PATCH] WORKDIR has same scope as FILESDIR and DISTDIR. by "Ulrich Müller"
1 As pointed out by mgorny [1], S really has the same scope as WORKDIR.
2 Updated patch below.
3
4 [1] https://bugs.gentoo.org/613110
5
6
7 From 46266df1bb3f6a1183a82e19740865fee877be76 Mon Sep 17 00:00:00 2001
8 From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <ulm@g.o>
9 Date: Sat, 18 Mar 2017 15:18:25 +0100
10 Subject: [PATCH v2] WORKDIR and S have the same scope as FILESDIR and DISTDIR.
11
12 Both WORKDIR and S are defined in global scope, but ebuilds must not
13 access the actual directories. So the FILESDIR footnote applies to
14 them, too. Rearrange the table accordingly.
15
16 Also small change of wording ("in which" -> "where") to prevent an
17 awkward page break.
18 ---
19 ebuild-env-vars.tex | 24 ++++++++++++------------
20 1 file changed, 12 insertions(+), 12 deletions(-)
21
22 diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex
23 index 262bcf9..6b6e1c9 100644
24 --- a/ebuild-env-vars.tex
25 +++ b/ebuild-env-vars.tex
26 @@ -95,6 +95,18 @@ variable.
27 Ditto &
28 Yes &
29 The full path to the directory in which the files in the \t{A} variable are stored. \\
30 +\t{WORKDIR} &
31 + Ditto &
32 + Yes &
33 + The full path to the ebuild's working directory, where all build data should be contained.%
34 + \label{env-var-WORKDIR} \\
35 +\t{S} &
36 + \t{src\_*} &
37 + Yes &
38 + The full path to the temporary build directory, used by \t{src\_compile}, \t{src\_install} etc.
39 + Defaults to \t{\$\{WORKDIR\}/\$\{P\}}. May be modified by ebuilds. If \t{S} is assigned in the
40 + global scope of an ebuild, then the restrictions of section~\ref{sec:ebuild-env-state} for
41 + global variables apply. \\
42 \t{PORTDIR} &
43 \t{src\_*} &
44 No &
45 @@ -190,18 +202,6 @@ variable.
46 was executed by the package manager. May be unset or any single word that is not any of the
47 above when the ebuild is being sourced for other (e.\,g.\ metadata or QA) purposes. Only for
48 EAPIs listed in table~\ref{tab:added-env-vars-table} as supporting \t{EBUILD\_PHASE\_FUNC}. \\
49 -\t{WORKDIR} &
50 - \t{src\_*}, global~scope &
51 - Yes &
52 - The full path to the ebuild's working directory, in which all build data should be
53 - contained. \label{env-var-WORKDIR} \\
54 -\t{S} &
55 - \t{src\_*} &
56 - Yes &
57 - The full path to the temporary build directory, used by \t{src\_compile}, \t{src\_install} etc.
58 - Defaults to \t{\$\{WORKDIR\}/\$\{P\}}. May be modified by ebuilds. If \t{S} is assigned in the
59 - global scope of an ebuild, then the restrictions of section~\ref{sec:ebuild-env-state} for
60 - global variables apply. \\
61 \t{KV} &
62 All &
63 Yes &
64 --
65 2.12.0

Replies