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)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 074FB158083 for ; Sun, 1 Sep 2024 13:45:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EF346E2A1E; Sun, 1 Sep 2024 13:45:13 +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 B308DE2A19 for ; Sun, 1 Sep 2024 13:45:13 +0000 (UTC) From: Ulrich Mueller To: gentoo-dev@lists.gentoo.org Cc: glep@gentoo.org Subject: [gentoo-dev] GLEP 83 "EAPI deprecation" update v2 In-Reply-To: (Ulrich Mueller's message of "Fri, 30 Aug 2024 18:21:57 +0200") References: Date: Sun, 01 Sep 2024 15:45:07 +0200 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: 09b8fe48-809c-48dd-8839-1d9c60ca87c2 X-Archives-Hash: b2118782212c37a83a8a8df561374b07 --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Type: text/plain Version 2. No material changes, but clarified wording and added an example. Thanks to robbat2 for his comments. Patch and full new text of the GLEP are attached below. --=-=-= Content-Type: text/plain; charset=utf-8 Content-Disposition: inline; filename=v2-0001-glep-0083-Allow-deprecation-when-only-one-newer-E.patch Content-Transfer-Encoding: quoted-printable From=2097fbff191d6b9a896d875f88f303816f7804a768 Mon Sep 17 00:00:00 2001 From: =3D?UTF-8?q?Ulrich=3D20M=3DC3=3DBCller?=3D Date: Fri, 30 Aug 2024 18:09:59 +0200 Subject: [PATCH v2] glep-0083: Allow deprecation when only one newer EAPI exists MIME-Version: 1.0 Content-Type: text/plain; charset=3DUTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Ulrich M=C3=BCller =2D-- glep-0083.rst | 31 ++++++++++++++++++++++++------- 1 file changed, 24 insertions(+), 7 deletions(-) diff --git a/glep-0083.rst b/glep-0083.rst index 38b4e57..5762d37 100644 =2D-- a/glep-0083.rst +++ b/glep-0083.rst @@ -6,8 +6,8 @@ Type: Informational Status: Active Version: 1 Created: 2022-06-30 =2DLast-Modified: 2022-08-14 =2DPost-History: 2022-07-11, 2022-07-31 +Last-Modified: 2024-09-01 +Post-History: 2022-07-11, 2022-07-31, 2024-08-30, 2024-09-01 Content-Type: text/x-rst --- =20 @@ -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]_. =20 =2DThe 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 =20 =2D* two newer Council-approved EAPIs are supported by the stable version =2D of Portage, and =2D* 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. =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 @@ -81,6 +84,20 @@ ebuild updates (and bug reports requesting them) managea= ble, as a banned EAPI is sufficient reason for updating an ebuild. =20 =20 +Example +=3D=3D=3D=3D=3D=3D=3D + +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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D-=20 2.46.0 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Disposition: inline; filename=glep-0083.rst Content-Transfer-Encoding: quoted-printable =2D-- GLEP: 83 Title: EAPI deprecation Author: Ulrich M=C3=BCller Type: Informational Status: Active Version: 1 Created: 2022-06-30 Last-Modified: 2024-09-01 Post-History: 2022-07-11, 2022-07-31, 2024-08-30, 2024-09-01 Content-Type: text/x-rst =2D-- Abstract =3D=3D=3D=3D=3D=3D=3D=3D Introduce standardized criteria for deprecation and banning of EAPIs. Motivation =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 Council will deprecate an EAPI when one or more newer Council-approved EAPIs are supported by the stable version of Portage, namely * 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 * 24 months have passed since its deprecation, and * it is used by fewer than 5 % of ebuilds in the Gentoo repository. EAPIs used in profiles are outside the scope of this GLEP. Rationale =3D=3D=3D=3D=3D=3D=3D=3D=3D Timing of EAPI deprecation is a trade-off between different factors. On the one hand, the total number of EAPIs in active use should be limited; this will prevent the learning curve for new developers and contributors from becoming too steep and will help to reduce code complexity, e.g. in eclasses. On the other hand, an upgrade path to a stable system is guaranteed for one year, plus limited support for systems that are outdated more than a year [#COUNCIL-20091109]_. Therefore, previous EAPIs are still required during that time. A period of 24 months before deprecation has been chosen, which is more than the required minimum and will 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. 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 overlays and downstream distributions. An additional requirement for banning an EAPI is that fewer than 5 % of ebuilds are using the EAPI in question. This requirement is defined to help keep the number of ebuild updates (and bug reports requesting them) manageable, as a banned EAPI is sufficient reason for updating an ebuild. Example =3D=3D=3D=3D=3D=3D=3D 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The following table compares the actual dates of deprecations and bans [#PMS-PROJECT]_ with the dates that would have resulted from the criteria proposed in this GLEP ("new date"). =3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D =3D=3D=3D=3D=3D=3D EAPI Portage Gentoo repo deprecated diff. banned = diff. =2D--- ---------- ----------- ----------------------- ------ ---------= -------------- ------ \ stable usage < 5 % actual date new date months actual date= new date months =3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D =3D=3D=3D=3D=3D=3D 0 2005-12-26 2017-02-28 2014-02-25 2009-12-11 -50 2016-01-10 = 2017-02-28 +14 1 2007-12-11 2009-10-25 2013-04-09 2011-01-08 -27 2014-03-11 = 2013-01-08 -14 2 2009-01-08 2015-03-27 2013-04-09 2012-03-08 -13 2014-03-11 = 2015-03-27 +12 3 2010-03-08 2015-01-16 2014-02-25 2013-03-17 -11 2016-01-10 = 2015-03-17 -10 4 2011-03-17 2018-01-11 2015-10-11 2016-01-17 +3 2018-04-08 = 2018-01-17 -3 5 2012-12-11 2021-06-15 2018-05-13 2018-06-27 +1 2021-08-08 = 2021-06-15 -2 6 2016-01-17 2022-11-06 2021-07-11 2021-07-05 0 = 2023-07-05 [*]_ 7 2018-06-27 8 2021-07-05 =3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D = =3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D =3D=3D=3D=3D=3D=3D .. [*] Extrapolated date, obtained by fitting data between 2021-01-01 and 2022-07-31 with an exponential function. References =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D .. [#COUNCIL-20130409] "EAPI deprecation", Gentoo Council meeting summary 2013-04-09 (https://projects.gentoo.org/council/meeting-logs/20130409-summary.txt). Note: The original quote says "Repoman" instead of "pkgcheck". .. [#COUNCIL-20140311] "Ban on EAPI 1 and 2 should extend to updating EAPI in existing ebuilds", Gentoo Council meeting summary 2014-03-11 (https://projects.gentoo.org/council/meeting-logs/20140311-summary.txt) .. [#COUNCIL-20091109] "Upgrade path for old systems", Gentoo Council meeting summary 2009-11-09 (https://projects.gentoo.org/council/meeting-logs/20091109-summary.txt) .. [#PMS-PROJECT] Gentoo Package Manager Specification project (https://wiki.gentoo.org/wiki/Project:Package_Manager_Specification#EAPI= _life_cycle) Copyright =3D=3D=3D=3D=3D=3D=3D=3D=3D This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/. --=-=-=-- --==-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFDBAEBCAAtFiEEtDnZ1O9xIP68rzDbUYgzUIhBXi4FAmbUb+MPHHVsbUBnZW50 b28ub3JnAAoJEFGIM1CIQV4uItwH/1vkdYMo32iwMN5Jf+Gf8zm6zhPdtwblFy4P bcy1Y0vaqqCr+nL6i1vCgueYlu+vTmaC6LpUMlfR0khia2LIX+0b8MgHyVQmS3dh mOoG60TVpT6gLbhIH9eXwDwEhJwEAYqqdcagMJaHc75a+jrFb1p7MOe/09s3t1kp FKKNoMjk54XObLSepf/RddAmMJTxf6CQUEUu0ePU+hZbPZaPUfMnHIlA4ZkWfeqm A8KDSDPohynwFa7rbGLHHbBaNa9PY2VcRUnSNFb452XovsSzcHA3UNUT4axxBtVz uHnr3U+HpLAS73RSCkTDq80FEu82ny5vhjKBJA+dpMDnXK2XFfg= =Ydx/ -----END PGP SIGNATURE----- --==-=-=--