Ciaran McCreesh wrote:
> 
> * what the plan is for Portage implementation of that feature, and the
>   likelihood of it making it
> 

We should have someone dedicated to seeing each item implemented. For
example someone from the council.

Follows a quick list with hopefully no brain farts. In general I
consider having pkg_pretend and use dep extensions enough for main
features and then we should also implemented all those easily doable
little changes.

> 
> This list might help for those who're scared of git:
> 
> 1) EAPI 3 has pkg_pretend.

critical

> 2) EAPI 3 supports slot operator dependencies

can be dropped

> 3) EAPI 3 has use dependency defaults

critical

> 4) PROPERTIES, DEFINED_PHASES mandatory in EAPI 3

can be dropped

> 5) EAPI 3 has a default src_install

can be dropped

> 6) EAPI 3 has controllable compression and docompress

critical

> 7) EAPI 3 has dodoc -r

critical

> 8) EAPI 3 requires doins support for symlinks

can be dropped

> 9) EAPI 3 bans || ( use? ( ... ) )

critical

> 10) dohard and dosed banned in EAPI 3

can be dropped

> 11) doinclude, newinclude for EAPI 3

can be dropped

> 12) EAPI 3 supports .xz, .tar.xz

easy so should be in

> 13) EAPI 3 has more econf arguments

easy so should be in

> 14) EAPI 3 supports pkg_info on installed packages

can be dropped

> 15) USE is stricter in EAPI 3

can be dropped

> 16) AA, KV gone in EAPI 3

easy so should be in

> 17) S to WORKDIR fallback conditional for EAPI 3

easy so should be in

> 18) EAPI 3 has unpack --if-compressed, new src_unpack

can be dropped

> 19) RDEPEND=DEPEND gone in EAPI 3

critical

> 20) EAPI 3 has doexample.

can be dropped

> 21) REPLACING_VERSIONS and REPLACED_BY_VERSION in EAPI 3

critical

> 22) EAPI 3 has nonfatal, utilities die
> 

can be dropped

Regards,
Petteri