As many of you know EAPI 3 has been waiting for Portage to implement it for many months now and I asked zmedico for his estimate on whether it will be done this year:
19:50 < Betelgeuse> zmedico: Let's put it this way. How likely in percentages is EAPI 2 this year? 19:50 < Betelgeuse> s/2/3/ 19:51 < zmedico> I'd give it 80% chance I guess As far as I understand paludis already has the features implemented so maybe we could give EAPI 3 some field testing in some overlays to see how it works in practice from ebuild writer point of view. Paludis does not recognize it atm but probably easy to get a new revision/version out: 20:01 < zmedico> Betelgeuse: I'd guess they could test it as EAPI=paludis-3_pre or something like that 20:01 < dleverton> Betelgeuse: it doesn't install the config file, just uses it for tests, so that's correct So what's the general sentiment for giving this some spin in overlays? Maybe having some usage would build some social pressure on zmedico :) Regards, Petteri
signature.asc
Description: OpenPGP digital signature
