| 1 |
>>>>> On Tue, 06 Jul 2021, Thomas Deutschmann wrote: |
| 2 |
|
| 3 |
> On 2021-07-05 12:17, Ulrich Mueller wrote: |
| 4 |
>> Now that EAPI is supported by stable Portage (3.0.20-r6 went stable |
| 5 |
>> on the last arch today), I would like to ask the council to deprecate |
| 6 |
>> EAPI 6, both for ebuilds and for profiles. |
| 7 |
|
| 8 |
> Could you please outline the consequences of that? |
| 9 |
|
| 10 |
> I mean, it's still allowed to rev bump an EAPI 6 ebuild to add an |
| 11 |
> important patch (like fixing a security vulnerability) or fix deps, |
| 12 |
> especially for non-maintainers without requiring ebuild to be ported |
| 13 |
> to a non-deprecated EAPI first, right? |
| 14 |
|
| 15 |
> I.e. "just like before". |
| 16 |
|
| 17 |
> You are not talking about changing that. |
| 18 |
|
| 19 |
Deprecated means that usage of the EAPI will be discouraged, and that |
| 20 |
QA tools (e.g. repoman) will warn about it. [1] |
| 21 |
|
| 22 |
Ulrich |
| 23 |
|
| 24 |
[1] https://projects.gentoo.org/council/meeting-logs/20130409-summary.txt |
Archives