From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 82BBC158083 for ; Sun, 8 Sep 2024 19:29:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A5D592BC02A; Sun, 8 Sep 2024 19:29:04 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8C5242BC02A for ; Sun, 8 Sep 2024 19:29:04 +0000 (UTC) Received: from oystercatcher.gentoo.org (oystercatcher.gentoo.org [148.251.78.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id CD8FE34309E for ; Sun, 8 Sep 2024 19:29:03 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id 69ABD14CA for ; Sun, 8 Sep 2024 19:29:02 +0000 (UTC) From: "Ulrich Müller" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Ulrich Müller" Message-ID: <1725823456.c2bf655fd1d5b29737e627a1aa4dafbea75d0ed2.ulm@gentoo> Subject: [gentoo-commits] data/glep:master commit in: / X-VCS-Repository: data/glep X-VCS-Files: glep-0083.rst X-VCS-Directories: / X-VCS-Committer: ulm X-VCS-Committer-Name: Ulrich Müller X-VCS-Revision: c2bf655fd1d5b29737e627a1aa4dafbea75d0ed2 X-VCS-Branch: master Date: Sun, 8 Sep 2024 19:29:02 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: d5840cea-5419-4408-acd4-0f10898ad3aa X-Archives-Hash: 665761df66fff2a427a91e6d3300f8bb commit: c2bf655fd1d5b29737e627a1aa4dafbea75d0ed2 Author: Ulrich Müller gentoo org> AuthorDate: Fri Aug 30 16:09:59 2024 +0000 Commit: Ulrich Müller gentoo org> CommitDate: Sun Sep 8 19:24:16 2024 +0000 URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=c2bf655f glep-0083: Allow deprecation when only one newer EAPI exists Approved by the council on 2024-09-08. Closes: https://bugs.gentoo.org/938755 Signed-off-by: Ulrich Müller gentoo.org> glep-0083.rst | 33 +++++++++++++++++++++++++-------- 1 file changed, 25 insertions(+), 8 deletions(-) diff --git a/glep-0083.rst b/glep-0083.rst index 38b4e57..3b538ee 100644 --- a/glep-0083.rst +++ b/glep-0083.rst @@ -4,10 +4,10 @@ Title: EAPI deprecation Author: Ulrich Müller Type: Informational Status: Active -Version: 1 +Version: 2 Created: 2022-06-30 -Last-Modified: 2022-08-14 -Post-History: 2022-07-11, 2022-07-31 +Last-Modified: 2024-09-08 +Post-History: 2022-07-11, 2022-07-31, 2024-08-30, 2024-09-01 Content-Type: text/x-rst --- @@ -38,11 +38,12 @@ warn about this [#COUNCIL-20130409]_. A *banned EAPI* must no longer be used, neither for new ebuilds, nor for updating of existing ebuilds [#COUNCIL-20140311]_. -The Gentoo Council will deprecate an EAPI when +The Gentoo Council will deprecate an EAPI when one or more newer +Council-approved EAPIs are supported by the stable version of Portage, +namely -* two newer Council-approved EAPIs are supported by the stable version - of Portage, and -* one of them has been supported for 24 months. +* two newer EAPIs, one of them supported for at least 24 months, or +* one newer EAPI, supported for at least 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 @@ -81,6 +84,20 @@ ebuild updates (and bug reports requesting them) manageable, as a banned EAPI is sufficient reason for updating an ebuild. +Example +======= + +Under this policy, EAPI 7 will be deprecated when either + +* Portage has supported EAPI 8 for 24 months, and supports another + later EAPI (e.g. EAPI 9), or +* Portage has supported EAPI 8 for 48 months. + +Portage has supported EAPI 8 since 2021-07-05. The first condition +would be fulfilled after 2023-07-05, as soon as an EAPI 9 is also +supported. The second condition would be fulfilled after 2025-07-05. + + Backwards Compatibility =======================