| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 09/28/2013 03:00 AM, Ulrich Mueller wrote: |
| 5 |
>>>>>> On Sat, 28 Sep 2013, heroxbd wrote: |
| 6 |
> |
| 7 |
>> I am revisiting this topic based on previous discussions[1,2,3]. |
| 8 |
> |
| 9 |
>> There seems to be a constant need for toolchain with a new EAPI. The |
| 10 |
>> only block is "how can we upgrade from an ancient system?", "don't |
| 11 |
>> bump or the upgrade path will be break". Let's figure out a solid |
| 12 |
>> upgrade path consciously, with a test farm of ancient systems, and |
| 13 |
>> then bump the EAPI of toolchain. |
| 14 |
> |
| 15 |
> The upgrade path is not at all what is blocking this. In its 20130409 |
| 16 |
> meeting, the council has (unanimously) decided: "EAPIs 0 to 2 are no |
| 17 |
> longer required for the upgrade path of users' systems." |
| 18 |
> |
| 19 |
> The reason why toolchain packages are still at EAPI 0 was explained in |
| 20 |
> this posting: |
| 21 |
> http://thread.gmane.org/gmane.linux.gentoo.project/2369/focus=2377 |
| 22 |
> |
| 23 |
> AFAICS, changing that is entirely the task of the toolchain team. |
| 24 |
> |
| 25 |
Yes, it is entirely the task of the toolchain team, and looks like |
| 26 |
heroxbd joined the toolchain team and would like to push the rest of his |
| 27 |
team for this update. Something I greatly thank him for. |
| 28 |
|
| 29 |
I don't think any dev wants to (or really could) force toolchain to |
| 30 |
update individually, however, if motivated people want to join the team |
| 31 |
and help, his question appeared to be will it be permitted to be updated. |
| 32 |
|
| 33 |
- -Zero |
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v2.0.20 (GNU/Linux) |
| 36 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 37 |
|
| 38 |
iQIcBAEBAgAGBQJSRwnhAAoJEKXdFCfdEflKVycP/RrDx0riRF9HO8yjMlPxPRmX |
| 39 |
Fm4xl+KdGNiKIxHDKVKGehyHDGyEVxUq8ZtrNqkQurtgibhtI2eErOjWYVHsV2Yj |
| 40 |
A2lW8JubwvYn14Qk0Pem9jg5cGTbo1mEA4UGG2XMWYzyGJkXi/m+alJYTQfZpbGk |
| 41 |
VKwll6wAMpPpVoV/xAA/mHX5AJrALQrP9/0xqOtvcSSvJTZvu4rpLFPWRlUf6Q6C |
| 42 |
Z+0grxc3x6Nq6Ryn6f39KLRYgXv6AEwx9ieajKu7ES+rBbTWsJCHtPD+H3zZbJI8 |
| 43 |
g+/2GPMgDmQ9tMQwuBwPdylUzGhPwd8Gmd6546mnBPOlZZNsJxBc/Cqt1paMyaPy |
| 44 |
sZp2igbXR5B9ha6Tg5bW7j6WDKqr9QZAslGYrXJa25wwmvcBQV+EsJrmmpQbDCdi |
| 45 |
todWjippnmJATDHVsHR1tW11/iO0t6UUKI8jLZm7HCaGXRptILWfICYYXAM19ntq |
| 46 |
9DWpA4BIpQzZx0s3cQZ1eIB3lHxPL387UWitAI9zW23Q0VYfddQgbLKbAo76GkR7 |
| 47 |
3ta6wjvIJ2vPBgxvv5Eo/hfKMUtxxyGeA/Jp6+zRMKPxcsqBocQXMs7pdmTON3Mb |
| 48 |
ddDLJ88tPc9QenHzE4PwCiTjSPDCSQRzrhmzt1iQEsIitVXDnL5kXGt38MfxT9We |
| 49 |
7p2PfdN8P4VekqKIcEVT |
| 50 |
=ROKo |
| 51 |
-----END PGP SIGNATURE----- |
Archives