Mailing List Archive

As discussed in #gentoo-portage yesterday: After a new EAPI has been
approved, there is a period during which there is no stable Portage
version supporting the new EAPI, and ebuilds for the new EAPI should
not be stabilised during that period. Add a new "eapis-testing" key
to layout.conf, so that development tools can warn about it.

Suggested-by: Micha? Górny <mgorny@gentoo.org>
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
glep-0082.rst | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/glep-0082.rst b/glep-0082.rst
index 6703313..61b0037 100644
--- a/glep-0082.rst
+++ b/glep-0082.rst
@@ -4,10 +4,10 @@ Title: Repository configuration file (layout.conf)
Author: Micha? Górny <mgorny@gentoo.org>
Type: Standards Track
Status: Draft
-Version: 1.0
+Version: 1.1
Created: 2021-05-19
-Last-Modified: 2021-05-31
-Post-History: 2021-05-19
+Last-Modified: 2021-06-18
+Post-History: 2021-05-19 2021-06-18
Content-Type: text/x-rst
---

@@ -159,6 +159,11 @@ eapis-banned = <space-separated EAPI names>
be blocked. If not specified, no EAPIs are banned. This key
does not apply to EAPI use in profiles.

+eapis-testing = <space-separated EAPI names>
+ Specifies one or more EAPIs that must not (yet) be used in ebuilds
+ with stable keywords, i.e. development tools should block their use
+ in such ebuilds.
+
repo-name = <string>
Specifies the repository name. If specified, it must be equal
to the contents of ``profiles/repo_name``. If not specified,
--
2.32.0