| 1 |
Hi all, |
| 2 |
|
| 3 |
with the discussion about EAPI3 we have now 4 (or 7, depending on how you |
| 4 |
count them ;) ) EAPIs available or almost available. This is getting quite |
| 5 |
confusing. |
| 6 |
To make our lives easier I would suggest deprecating EAPI0 and migrating |
| 7 |
existing ebuilds over some time to EAPI1 or higher until EAPI0 can be |
| 8 |
obsoleted at some point in the future. |
| 9 |
I would set the start of deprecation warnings about 3 months from now and the |
| 10 |
obsoletion quite a time later, maybe 12 months from now, when a sufficient |
| 11 |
amount of ebuilds has been migrated. |
| 12 |
|
| 13 |
Deprecating EAPI1 at the same time would reduce the amount of EAPIs we have to |
| 14 |
think about, but since it has some changes like adding src_prepare migration |
| 15 |
would not be as trivial. So I'd prefer keeping it around a bit longer. |
| 16 |
|
| 17 |
Comments? |
| 18 |
|
| 19 |
|
| 20 |
Patrick |
Archives