Gentoo Archives: gentoo-commits

From: "Ulrich Müller" <ulm@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/variables/
Date: Tue, 30 Mar 2021 07:21:07
Message-Id: 1617088841.206a502dbb146687f60b3cd171ac98aea6bfabe6.ulm@gentoo
1 commit: 206a502dbb146687f60b3cd171ac98aea6bfabe6
2 Author: Sam James <sam <AT> gentoo <DOT> org>
3 AuthorDate: Sun Mar 21 05:06:12 2021 +0000
4 Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
5 CommitDate: Tue Mar 30 07:20:41 2021 +0000
6 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=206a502d
7
8 ebuild-writing/variables: mention PMS for acceptable RESTRICT values
9
10 Signed-off-by: Sam James <sam <AT> gentoo.org>
11 Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
12
13 ebuild-writing/variables/text.xml | 18 ++++++++++++++++++
14 1 file changed, 18 insertions(+)
15
16 diff --git a/ebuild-writing/variables/text.xml b/ebuild-writing/variables/text.xml
17 index ed62185..55cc3bd 100644
18 --- a/ebuild-writing/variables/text.xml
19 +++ b/ebuild-writing/variables/text.xml
20 @@ -524,6 +524,24 @@ GLEP 23</uri> for details.
21 </body>
22 </section>
23
24 +<section>
25 +<title>RESTRICT</title>
26 +<body>
27 +
28 +<p>
29 +While Portage may recognise several different <c>RESTRICT</c> tokens, it is
30 +important that you do not rely on them existing. That is, you should ensure
31 +your ebuild does not fail if those tokens are not exposed or given a different
32 +name by another package manager. You can make use of Portage-provided
33 +<c>RESTRICT</c> tokens, but do not fail hard without them. See
34 +<uri link="https://projects.gentoo.org/pms/7/pms.html#x1-810008.2.8">
35 +PMS</uri> for the list of standardised <c>RESTRICT</c> tokens, or the above
36 +table.
37 +</p>
38 +
39 +</body>
40 +</section>
41 +
42 <section>
43 <title>ROOT</title>
44 <body>