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 09C0C158094 for ; Sat, 16 Jul 2022 07:04:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 13888E0F1D; Sat, 16 Jul 2022 07:04:52 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.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) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EB5D1E0F1D for ; Sat, 16 Jul 2022 07:04:51 +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) server-digest SHA256) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 0BAE7340FFF for ; Sat, 16 Jul 2022 07:04:51 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id 6D371535 for ; Sat, 16 Jul 2022 07:04:49 +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: <1657954965.fee3ef8459482d515a4cfaf2308558ac8d279ccf.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: fee3ef8459482d515a4cfaf2308558ac8d279ccf X-VCS-Branch: master Date: Sat, 16 Jul 2022 07:04:49 +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: 4a05983c-5a7a-4138-923b-d0db2d4a949a X-Archives-Hash: 56f541dfe2bbb1fb2f7d44f277292bc5 commit: fee3ef8459482d515a4cfaf2308558ac8d279ccf Author: Ulrich Müller gentoo org> AuthorDate: Sat Jul 16 07:02:45 2022 +0000 Commit: Ulrich Müller gentoo org> CommitDate: Sat Jul 16 07:02:45 2022 +0000 URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=fee3ef84 glep-0083: Whitespace Signed-off-by: Ulrich Müller gentoo.org> glep-0083.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/glep-0083.rst b/glep-0083.rst index 3f9b259..f2a55a3 100644 --- a/glep-0083.rst +++ b/glep-0083.rst @@ -22,17 +22,17 @@ Motivation ========== So far, old EAPIs were deprecated by the Gentoo Council in an ad-hoc -manner. No fixed criteria were used, resulting in very different -deprecation times after approval of newer EAPIs. Standardized criteria -for deprecation and banning will make the life cycle of EAPIs more -predictable. +manner. No fixed criteria were used, resulting in very different +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 +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 @@ -60,8 +60,8 @@ 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 +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. @@ -70,8 +70,8 @@ are otherwise seldom updated to be bumped to the next but one EAPI immediately. 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. Since a banned EAPI is +authors enough time to update. This is especially relevant for +overlays and downstream distributions. Since a banned EAPI is sufficient reason for updating an ebuild, an additional threshold of 5 % is required, in order to keep the number of such updates (and bug reports requesting them) manageable.