|
Lines 6-13
Type: Informational
Link Here
|
| 6 |
Status: Active |
6 |
Status: Active |
| 7 |
Version: 1 |
7 |
Version: 1 |
| 8 |
Created: 2022-06-30 |
8 |
Created: 2022-06-30 |
| 9 |
Last-Modified: 2022-08-14 |
9 |
Last-Modified: 2024-09-01 |
| 10 |
Post-History: 2022-07-11, 2022-07-31 |
10 |
Post-History: 2022-07-11, 2022-07-31, 2024-08-30, 2024-09-01 |
| 11 |
Content-Type: text/x-rst |
11 |
Content-Type: text/x-rst |
| 12 |
--- |
12 |
--- |
| 13 |
|
13 |
|
|
Lines 38-48
warn about this [#COUNCIL-20130409]_.
Link Here
|
| 38 |
A *banned EAPI* must no longer be used, neither for new ebuilds, nor |
38 |
A *banned EAPI* must no longer be used, neither for new ebuilds, nor |
| 39 |
for updating of existing ebuilds [#COUNCIL-20140311]_. |
39 |
for updating of existing ebuilds [#COUNCIL-20140311]_. |
| 40 |
|
40 |
|
| 41 |
The Gentoo Council will deprecate an EAPI when |
41 |
The Gentoo Council will deprecate an EAPI when one or more newer |
|
|
42 |
Council-approved EAPIs are supported by the stable version of Portage, |
| 43 |
namely |
| 42 |
|
44 |
|
| 43 |
* two newer Council-approved EAPIs are supported by the stable version |
45 |
* two newer EAPIs, one of them supported for at least 24 months, or |
| 44 |
of Portage, and |
46 |
* one newer EAPI, supported for at least 48 months. |
| 45 |
* one of them has been supported for 24 months. |
|
|
| 46 |
|
47 |
|
| 47 |
The Gentoo Council will ban a deprecated EAPI when |
48 |
The Gentoo Council will ban a deprecated EAPI when |
| 48 |
|
49 |
|
|
Lines 70-76
allow projects to support a longer upgrade path.
Link Here
|
| 70 |
|
71 |
|
| 71 |
Requiring two newer EAPIs before deprecation will allow ebuilds that |
72 |
Requiring two newer EAPIs before deprecation will allow ebuilds that |
| 72 |
are otherwise seldom updated to be bumped to the next but one EAPI |
73 |
are otherwise seldom updated to be bumped to the next but one EAPI |
| 73 |
immediately. |
74 |
immediately. However, deprecation of an EAPI should not be deferred |
|
|
75 |
forever, so it can be effected after a longer waiting period of 48 |
| 76 |
months even if only one newer EAPI exists at that point. |
| 74 |
|
77 |
|
| 75 |
A delay of 24 months between deprecation and ban will give ebuild |
78 |
A delay of 24 months between deprecation and ban will give ebuild |
| 76 |
authors enough time to update. This is especially relevant for |
79 |
authors enough time to update. This is especially relevant for |
|
Lines 81-86
ebuild updates (and bug reports requesting them) manageable, as a
Link Here
|
| 81 |
banned EAPI is sufficient reason for updating an ebuild. |
84 |
banned EAPI is sufficient reason for updating an ebuild. |
| 82 |
|
85 |
|
| 83 |
|
86 |
|
|
|
87 |
Example |
| 88 |
======= |
| 89 |
|
| 90 |
Under this policy, EAPI 7 will be deprecated when either |
| 91 |
|
| 92 |
* Portage has supported EAPI 8 for 24 months, and supports another |
| 93 |
later EAPI (e.g. EAPI 9), or |
| 94 |
* Portage has supported EAPI 8 for 48 months. |
| 95 |
|
| 96 |
Portage has supported EAPI 8 since 2021-07-05. The first condition |
| 97 |
would be fulfilled after 2023-07-05, as soon as an EAPI 9 is also |
| 98 |
supported. The second condition would be fulfilled after 2025-07-05. |
| 99 |
|
| 100 |
|
| 84 |
Backwards Compatibility |
101 |
Backwards Compatibility |
| 85 |
======================= |
102 |
======================= |
| 86 |
|
103 |
|
| 87 |
- |
|
|
