| 1 |
On 2021-07-05 12:17, Ulrich Mueller wrote: |
| 2 |
> Now that EAPI is supported by stable Portage (3.0.20-r6 went stable |
| 3 |
> on the last arch today), I would like to ask the council to deprecate |
| 4 |
> EAPI 6, both for ebuilds and for profiles. |
| 5 |
|
| 6 |
Could you please outline the consequences of that? |
| 7 |
|
| 8 |
I mean, it's still allowed to rev bump an EAPI 6 ebuild to add an |
| 9 |
important patch (like fixing a security vulnerability) or fix deps, |
| 10 |
especially for non-maintainers without requiring ebuild to be ported to |
| 11 |
a non-deprecated EAPI first, right? |
| 12 |
|
| 13 |
I.e. "just like before". |
| 14 |
|
| 15 |
You are not talking about changing that. |
| 16 |
|
| 17 |
|
| 18 |
-- |
| 19 |
Regards, |
| 20 |
Thomas Deutschmann / Gentoo Linux Developer |
| 21 |
fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 |
Archives