1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
2 |
Hash: SHA256
|
3 |
|
4 |
On Tue, 17 Nov 2015 23:09:34 +0100
|
5 |
Michał Górny <mgorny@g.o> wrote:
|
6 |
|
7 |
> Fellow Developers! |
8 |
> |
9 |
> I have the pleasure to announce that portage-2.2.25 has just been |
10 |
> committed and it comes with complete EAPI 6 support. This effectively |
11 |
> means that from this moment forward Gentoo developers are permitted to |
12 |
> commit EAPI 6 ebuilds to ~arch. |
13 |
> |
14 |
> Some quick notes: |
15 |
> |
16 |
> 1. Remember that you can't stabilize ebuilds using EAPI 6. Therefore, |
17 |
> if you go for EAPI 6, you ebuild may be forced to stay ~arch for quite |
18 |
> a while. |
19 |
> |
20 |
> 2. The Portage implementation needs more testing and can be buggy. |
21 |
> Write ebuilds according to the spec, not Portage behavior or they will |
22 |
> fail. |
23 |
> |
24 |
> 2a. It just occurred to me that Portage does not fail when eapply_user |
25 |
> is not called. This is a bug, so make sure to call it or |
26 |
> default_src_prepare. |
27 |
> |
28 |
> 3. EAPI 6 is not a drop-in replacement for EAPI 5. Study it to use it |
29 |
> efficiently. Use it as an opportunity to improve the API of your |
30 |
> eclasses. |
31 |
> |
32 |
> 4. I've written an extensive guide [1] with some explanations |
33 |
> and rationale for many of the features. Consider it a must-read. |
34 |
> |
35 |
> 4a. We need someone to update the devmanual. |
36 |
> |
37 |
> [1]:https://blogs.gentoo.org/mgorny/2015/11/13/the-ultimate-guide-to-eapi-6/ |
38 |
> |
39 |
|
40 |
I just read your guide. What's the recommended manner to upgrade an
|
41 |
ebuild from the autotools-utils eclass? General advice would be
|
42 |
preferred, but I'm specifically looking at app-emulation/wine.
|
43 |
|
44 |
- --
|
45 |
NP-Hardass
|
46 |
-----BEGIN PGP SIGNATURE-----
|
47 |
Version: GnuPG v2
|
48 |
|
49 |
iQIcBAEBCAAGBQJWS9JkAAoJEBzZQR2yrxj7ckQQAIUSzSkOOv+b6ukMkx4xtTCV
|
50 |
DsjanXXgRy68zKxhLAWn03j6qWXiM2KYaTD6Mnj8anV63+NjfL46Yke9GHZTtjGu
|
51 |
tP1du8fmD1e0RNk0XjetaacEY00LU6EqxmRlFn0SmeGCFraCew5mrkTJToKFhDA8
|
52 |
95Oab1hvvfrZzLVnZC5AW+YEeJySfCaHRFrvqC3o8fLvbeun+d3sN7n/i5PYvIed
|
53 |
1VnJkW2cuLixcLgJTxXJ4E4/xUcJpL7kCwPh0IJABir3EgtCIgqLnVD2TUPPDjAd
|
54 |
mOogB+v1f3D5hZk7w+tLbQ8OY2OpCbOk6h/0JiWvAWnOqC8JYkOxxAUgWPfWgIFr
|
55 |
5pRsMSfZO1N0D3VxB71PIfgAsPp8PKv8sLdlJWJkGhHFm7M0zyQ6ElpbRgFq0Xx6
|
56 |
awWYDFpVp8qdXN1zkxD14S68WHPGaD5QCJAnIbL9XMFY+03GQuJJxI66vJjpBCo+
|
57 |
3Q/skdDX/TGhj/M+jehB50IsSHiIstsiXpLtdew9htf89pkJZkt6A4KYd4/M9YC3
|
58 |
C7HX5np2pZgTSc/N2J6/0AST0k0n7l+PseDAyKWMO0ShdMv+oKtxmaW51qIupVoJ
|
59 |
e4ybFLsQd0h3KdP5e6YmOtWv0AYaMczChcFlqLHLWUrAxD622PsESqLX8qigTC1W
|
60 |
65FwvabVNa+WgDgxhzNC
|
61 |
=pWAw
|
62 |
-----END PGP SIGNATURE----- |