| 1 |
Fellow Developers! |
| 2 |
|
| 3 |
I have the pleasure to announce that portage-2.2.25 has just been |
| 4 |
committed and it comes with complete EAPI 6 support. This effectively |
| 5 |
means that from this moment forward Gentoo developers are permitted to |
| 6 |
commit EAPI 6 ebuilds to ~arch. |
| 7 |
|
| 8 |
Some quick notes: |
| 9 |
|
| 10 |
1. Remember that you can't stabilize ebuilds using EAPI 6. Therefore, |
| 11 |
if you go for EAPI 6, you ebuild may be forced to stay ~arch for quite |
| 12 |
a while. |
| 13 |
|
| 14 |
2. The Portage implementation needs more testing and can be buggy. |
| 15 |
Write ebuilds according to the spec, not Portage behavior or they will |
| 16 |
fail. |
| 17 |
|
| 18 |
2a. It just occurred to me that Portage does not fail when eapply_user |
| 19 |
is not called. This is a bug, so make sure to call it or |
| 20 |
default_src_prepare. |
| 21 |
|
| 22 |
3. EAPI 6 is not a drop-in replacement for EAPI 5. Study it to use it |
| 23 |
efficiently. Use it as an opportunity to improve the API of your |
| 24 |
eclasses. |
| 25 |
|
| 26 |
4. I've written an extensive guide [1] with some explanations |
| 27 |
and rationale for many of the features. Consider it a must-read. |
| 28 |
|
| 29 |
4a. We need someone to update the devmanual. |
| 30 |
|
| 31 |
[1]:https://blogs.gentoo.org/mgorny/2015/11/13/the-ultimate-guide-to-eapi-6/ |
| 32 |
|
| 33 |
-- |
| 34 |
Best regards, |
| 35 |
Michał Górny |
| 36 |
<http://dev.gentoo.org/~mgorny/> |
Archives