Gentoo Archives: gentoo-pms

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

Replies