From a1177143b51a374d0acda06915047b7573203a84 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ulrich=20M=C3=BCller?= Date: Fri, 30 Aug 2024 18:09:59 +0200 Subject: [PATCH] glep-0083: Allow deprecation when only one newer EAPI exists MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Ulrich Müller --- glep-0083.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/glep-0083.rst b/glep-0083.rst index 38b4e57..f542170 100644 --- a/glep-0083.rst +++ b/glep-0083.rst @@ -6,7 +6,7 @@ Type: Informational Status: Active Version: 1 Created: 2022-06-30 -Last-Modified: 2022-08-14 +Last-Modified: 2024-08-30 Post-History: 2022-07-11, 2022-07-31 Content-Type: text/x-rst --- @@ -42,7 +42,8 @@ The Gentoo Council will deprecate an EAPI when * two newer Council-approved EAPIs are supported by the stable version of Portage, and -* one of them has been supported for 24 months. +* one of them has been supported for 24 months; or +* one newer Council-approved EAPI has been supported for 48 months. The Gentoo Council will ban a deprecated EAPI when @@ -70,7 +71,9 @@ allow projects to support a longer upgrade path. Requiring two newer EAPIs before deprecation will allow ebuilds that are otherwise seldom updated to be bumped to the next but one EAPI -immediately. +immediately. However, deprecation of an EAPI should not be deferred +forever, so it can be effected after a longer waiting period of 48 +months even if only one newer EAPI exists at that point. A delay of 24 months between deprecation and ban will give ebuild authors enough time to update. This is especially relevant for -- 2.46.0