| 1 |
commit: cb08149b6689fd23aa92f3e0f0b0d835a10523b6 |
| 2 |
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Sun Jul 31 21:18:14 2022 +0000 |
| 4 |
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Sun Jul 31 21:18:14 2022 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=cb08149b |
| 7 |
|
| 8 |
glep-0083: Grammatical corrections |
| 9 |
|
| 10 |
Suggested-by: Thomas Bracht Laumann Jespersen <t <AT> laumann.xyz> |
| 11 |
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org> |
| 12 |
|
| 13 |
glep-0083.rst | 13 +++++++------ |
| 14 |
1 file changed, 7 insertions(+), 6 deletions(-) |
| 15 |
|
| 16 |
diff --git a/glep-0083.rst b/glep-0083.rst |
| 17 |
index 7050b25..0980124 100644 |
| 18 |
--- a/glep-0083.rst |
| 19 |
+++ b/glep-0083.rst |
| 20 |
@@ -22,7 +22,7 @@ Motivation |
| 21 |
========== |
| 22 |
|
| 23 |
So far, old EAPIs were deprecated by the Gentoo Council in an ad-hoc |
| 24 |
-manner. No fixed criteria were used, resulting in very different |
| 25 |
+manner. No fixed criteria were used, resulting in unpredictable |
| 26 |
deprecation times after approval of newer EAPIs. Standardized |
| 27 |
criteria for deprecation and banning will make the life cycle of EAPIs |
| 28 |
more predictable. |
| 29 |
@@ -47,7 +47,7 @@ The Gentoo Council will deprecate an EAPI when |
| 30 |
The Gentoo Council will ban a deprecated EAPI when |
| 31 |
|
| 32 |
* 24 months have passed since its deprecation, and |
| 33 |
-* it is used by less than 5 % of ebuilds in the Gentoo repository. |
| 34 |
+* it is used by fewer than 5 % of ebuilds in the Gentoo repository. |
| 35 |
|
| 36 |
EAPIs used in profiles are outside the scope of this GLEP. |
| 37 |
|
| 38 |
@@ -74,10 +74,11 @@ immediately. |
| 39 |
|
| 40 |
A delay of 24 months between deprecation and ban will give ebuild |
| 41 |
authors enough time to update. This is especially relevant for |
| 42 |
-overlays and downstream distributions. Since a banned EAPI is |
| 43 |
-sufficient reason for updating an ebuild, an additional threshold of |
| 44 |
-5 % is required, in order to keep the number of such updates (and bug |
| 45 |
-reports requesting them) manageable. |
| 46 |
+overlays and downstream distributions. An additional requirement for |
| 47 |
+banning an EAPI is that fewer than 5 % of ebuilds are using the EAPI |
| 48 |
+in question. This requirement is defined to help keep the number of |
| 49 |
+ebuild updates (and bug reports requesting them) managable, as a |
| 50 |
+banned EAPI is sufficient reason for updating an ebuild. |
| 51 |
|
| 52 |
|
| 53 |
Backwards Compatibility |
Archives