-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/28/2013 10:12 PM, hero...@gentoo.org wrote: > "Rick \"Zero_Chaos\" Farina" <zeroch...@gentoo.org> writes: > >> On 09/28/2013 03:00 AM, Ulrich Mueller wrote: >>>>>>>> On Sat, 28 Sep 2013, heroxbd wrote: >>> >>>> I am revisiting this topic based on previous discussions[1,2,3]. >>> >>>> There seems to be a constant need for toolchain with a new EAPI. The >>>> only block is "how can we upgrade from an ancient system?", "don't >>>> bump or the upgrade path will be break". Let's figure out a solid >>>> upgrade path consciously, with a test farm of ancient systems, and >>>> then bump the EAPI of toolchain. >>> >>> The upgrade path is not at all what is blocking this. In its 20130409 >>> meeting, the council has (unanimously) decided: "EAPIs 0 to 2 are no >>> longer required for the upgrade path of users' systems." >>> >>> The reason why toolchain packages are still at EAPI 0 was explained in >>> this posting: >>> http://thread.gmane.org/gmane.linux.gentoo.project/2369/focus=2377 >>> >>> AFAICS, changing that is entirely the task of the toolchain team. > > Thank you for the clarification, Ulrich. > >> Yes, it is entirely the task of the toolchain team, and looks like >> heroxbd joined the toolchain team and would like to push the rest of his >> team for this update. Something I greatly thank him for. >> >> I don't think any dev wants to (or really could) force toolchain to >> update individually, however, if motivated people want to join the team >> and help, his question appeared to be will it be permitted to be >> updated. > > Can't agree with you more. > > It's just a starting point, though. I still don't have a clear plan yet. > > After reading carefully the thread Ulrich pointed out, it seems that > refactoring ebuild/eclass is invevitable, which calls for an overlay to > carry it on. > While I'm not nearly good enough to detail how this should happen exactly, please, may I beg, do an eclass revision for this. The fact that this hasn't been done clearly implies it is a lot of work. Let's not risk stable, let's simply make toolchain-r1.eclass or whatever, and bump that to eapi5. At the end of the day, this allows working and testing without odd issues, and if everyone really hates that idea you can simply drop the changes into the original eclass when it's all done.
Thanks, Zero -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSR5V3AAoJEKXdFCfdEflKDcMP/0B01NSlVaTEM6oDIF324YNP p1G1vNVh86avVCL+0sLfmDPID547qWZOfemoids94xemrvyVYnJFccvtg7KBH+ck k4h/LJ2pTEvCGiL3KyUngYc6XN3YMwOHJsRD+jr0cmYG+GG0Lm5UUb73PPhgLtOv Ltrm4B68w3x1qqucrd3/PgBF7tfjoBdvB8XqkJ+u9RoMFfFb2BUH3n6VZ2Ngkzup BU5PaakC8tBGhZvkLrd81RHTY7iHuM5HGh4ZK0GSfVsq+pYIwFpWztKGcSQmEpxe oLgMZD2g5GAykkUhzcrvc6p091wsOylenAgnhZZL2cy2pZE99TLTUw6y/Q7+HUiN mKdXG/JbXQ/FmkhqVivvWM43g3bumEvYub5EegUa6MGrHjCqRjsO+GQq68CGTbMq TYpZXUGtCdAdMIyvk6wMhTWlrO2TQmakkj/tqHif1TsyVIIYZlTKLosftqxVbpxd 54Mr1oI+LM7oHGghy5/7BJz0V0U7BWIXiDBBf4HJ1k4gybkRBqCx7I+YSYib9ZZg jvHwJv9kiksduO5dQk/NmKgWgmyBTaYzZYPvxJyXp2uzk3Nmgf7JAwN2AHuUrFXZ 5LLwPC36bwEyAdKABHwIZsVdquBm2smFLIFy4oMoxcmEHBaOmOKBSrIKN0iLPYnD ZfpgorrlwCLdiqV+VeKU =jY8E -----END PGP SIGNATURE-----
