-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 13/01/14 12:02, Steven J. Long wrote: > Yeah but it already outshines under the hood: all you're talking > about is EAPI and radhermit is working on it; I'm sure he and > dol-sen would be happy for more help as well, so long as it's > supportive. ISTR TomWij is involved too. I know all this. But until the EAPI is brought up to date, I don't see a lot of devs migrating their work there. (Kudos to radhermit for his work.) Furthermore, bringing the EAPI up to date is not of ignorable complexity.
> Updating both in parallel isn't hard: once pkgcore is up to EAPI-5, > EAPI-6 isn't that much work (mostly bash afair.) If it is trivial: show us the code. > At that point, put portage into feature-freeze, and only bugfix it. > Call a hiatus on new EAPIs for 6 months and put all effort into > making damn sure pkgcore is a drop-in replacement. I don't see this happening as it stands right now. Let's revisit this when pkgcore is more up to date. > There's certainly enough devs to do that, and definitely enough > interest in finally moving to portage-NG. These are two big statements, and I'm not convinced either of them holds true. Feel free to gather data on the latter. (The former is not immediately quantifiable.) - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlLT290ACgkQRtClrXBQc7XeuAD+Jj4Oj73br8pvcKdkDSVFfE3J tG6ajS3wzQHNmkbxWPoA+gMVyzgm5SSDRAjqHysocgvvDe6Xwa2CA+/ON98u+2xs =mBxD -----END PGP SIGNATURE-----
