commit:     206a502dbb146687f60b3cd171ac98aea6bfabe6
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 05:06:12 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Mar 30 07:20:41 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=206a502d

ebuild-writing/variables: mention PMS for acceptable RESTRICT values

Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 ebuild-writing/variables/text.xml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/ebuild-writing/variables/text.xml 
b/ebuild-writing/variables/text.xml
index ed62185..55cc3bd 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -524,6 +524,24 @@ GLEP 23</uri> for details.
 </body>
 </section>
 
+<section>
+<title>RESTRICT</title>
+<body>
+
+<p>
+While Portage may recognise several different <c>RESTRICT</c> tokens, it is
+important that you do not rely on them existing. That is, you should ensure
+your ebuild does not fail if those tokens are not exposed or given a different
+name by another package manager. You can make use of Portage-provided
+<c>RESTRICT</c> tokens, but do not fail hard without them. See
+<uri link="https://projects.gentoo.org/pms/7/pms.html#x1-810008.2.8";>
+PMS</uri> for the list of standardised <c>RESTRICT</c> tokens, or the above
+table.
+</p>
+
+</body>
+</section>
+
 <section>
 <title>ROOT</title>
 <body>

Reply via email to