--=-=-=
Content-Type: text/plain

Deprecation of an EAPI should not be deferred forever. This update of
GLEP 83 will allow it after a longer waiting period of 48 months even if
only one newer EAPI would exist at that point.


--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline;
filename=0001-glep-0083-Allow-deprecation-when-only-one-newer-EAPI.patch Content-Transfer-Encoding: quoted-printable

From a1177143b51a374d0acda06915047b7573203a84 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <ulm@gentoo.org>
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=C3=BCller <ulm@gentoo.org>
=2D--
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
=2D-- a/glep-0083.rst
+++ b/glep-0083.rst
@@ -6,7 +6,7 @@ Type: Informational
Status: Active
Version: 1
Created: 2022-06-30
=2DLast-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
=20
* two newer Council-approved EAPIs are supported by the stable version
of Portage, and
=2D* 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.
=20
The Gentoo Council will ban a deprecated EAPI when
=20
@@ -70,7 +71,9 @@ allow projects to support a longer upgrade path.
=20
Requiring two newer EAPIs before deprecation will allow ebuilds that
are otherwise seldom updated to be bumped to the next but one EAPI =2Dimmediately.
+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.
=20
A delay of 24 months between deprecation and ban will give ebuild
authors enough time to update. This is especially relevant for
=2D-=20
2.46.0


--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline; filename=glep-0083.rst
Content-Transfer-Encoding: quoted-printable

---
GLEP: 83
Title: EAPI deprecation
Author: Ulrich Müller <ulm@gentoo.org>
Type: Informational
Status: Active
Version: 1
Created: 2022-06-30
Last-Modified: 2024-08-30
Post-History: 2022-07-11, 2022-07-31
Content-Type: text/x-rst
---


Abstract
========

Introduce standardized criteria for deprecation and banning of EAPIs.


Motivation
==========

So far, old EAPIs were deprecated by the Gentoo Council in an ad-hoc
manner. No fixed criteria were used, resulting in unpredictable
deprecation times after approval of newer EAPIs. Standardized
criteria for deprecation and banning will make the life cycle of EAPIs
more predictable.


Specification
=============

A *deprecated EAPI* is no longer required for the upgrade path of
users' systems. Its use is discouraged, and tools like pkgcheck will
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 Counc