Am Sonntag, den 22.03.2009, 20:38 +0000 schrieb Ciaran McCreesh:
> On Sun, 22 Mar 2009 21:18:52 +0100
> Donnie Berkholz <dberkholz@g.o> wrote:
> > If you have something you'd wish for us to chat about, maybe even vote
> > on, let us know! Simply reply to this e-mail for the whole Gentoo dev
> > list to see.
> 
> Continuing the whole EAPI 3 thing...
> 
> http://github.com/ciaranm/pms/tree/eapi-3 is a draft based upon
> ongoing discussion. There's more or less one commit per new feature. For
> each feature, I'd like to know:
> 
> * whether there are any objections to that feature as a candidate for
>   EAPI 3
> 
> * what the plan is for Portage implementation of that feature, and the
>   likelihood of it making it
I already started to implement small proposals for portage. For some
issues some minor structural/architectural have to be made.

> 
> * whether that feature is considered critical for EAPI 3, or whether it
>   can be dropped if necessary if Portage can't get it implemented
>   within a certain time
> 
> Also, I'd like to know of any potential omissions.
> 
> I'd imagine this'd go easier of Council members went through before the
> meeting and provided individual opinions on each item, and then just
> discussed any disagreements during the meeting, but whatever's best for
> you...
> 
> This list might help for those who're scared of git:
> 
> 1) EAPI 3 has pkg_pretend.
We have to write something here (probably not in PMS but in the
devmanual) to make clear what is allowed in pkg_pretend and what not.

> 2) EAPI 3 supports slot operator dependencies
> 3) EAPI 3 has use dependency defaults
> 4) PROPERTIES, DEFINED_PHASES mandatory in EAPI 3
> 5) EAPI 3 has a default src_install
Spec needed. DOCS or no DOCS?

> 6) EAPI 3 has controllable compression and docompress
> 7) EAPI 3 has dodoc -r
> 8) EAPI 3 requires doins support for symlinks
Current behaviour is to copy the file the symlink points to, right?
Is that behaviour unsafe and should be deprecated completely or do we
add a flag turning on the new/the old behaviour?

> 9) EAPI 3 bans || ( use? ( ... ) )
> 10) dohard and dosed banned in EAPI 3
> 11) doinclude, newinclude for EAPI 3
> 12) EAPI 3 supports .xz, .tar.xz
> 13) EAPI 3 has more econf arguments
> 14) EAPI 3 supports pkg_info on installed packages
you probably mean: uninstalled

> 15) USE is stricter in EAPI 3
Proper documentation for IUSE_IMPLICIT/USE_EXPAND_IMPLICIT is needed. In
the PMS draft there's only a reference to section 11.1.1, but in that
section is nothing about it.

> 16) AA, KV gone in EAPI 3
> 17) S to WORKDIR fallback conditional for EAPI 3
> 18) EAPI 3 has unpack --if-compressed, new src_unpack
> 19) RDEPEND=DEPEND gone in EAPI 3
> 20) EAPI 3 has doexample.
Including "-r" or implicit recursive?

> 21) REPLACING_VERSIONS and REPLACED_BY_VERSION in EAPI 3
Same thing as for 1)

> 22) EAPI 3 has nonfatal, utilities die

... and we've got most (if not all) proposals with reasons documented
here:
  http://dev.gentoo.org/~dev-zero/docs/EAPI3.html

Cheers,
Tiziano