-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ryan Hill wrote: > Zac Medico wrote: >> As for using things like IUSE defaults and SLOT dependencies in >> ebuilds (both supported by portage-2.1.2), the most backward >> compatible approach is to do an EAPI bump. We should probably >> include a few other things in the EAPI-1 bump [1] that aren't >> implemented yet. We don't have to include everything that's planned, >> but it would be good to include at least some of the simplest features. > > SLOT depends are something we could really use right now. What kind of > time frame are you thinking of?
Trying to include things that aren't implemented or things that are controversial will delay it. It's difficult to make time estimates for anything that's not implemented yet. It's trivial to do the EAPI-1 bump if we only include things that are already implemented. I can have a sys-apps/portage release in the tree this week with EAPI-1 support if we choose to do that. Looking at bug #174380, I'd say that EAPI-1 should certainly include #174405, #174410, and #179380 since they're all implemented and relatively non-controversial. Anything more than those can lead to potential delays. Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHA8VV/ejvha5XGaMRAjVmAKDYi/BX6HU/v8B0Mf8l6qfschmyjgCfbBdq cj2yldMRM+saK8KnKKi7UF4= =+efu -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
