Am Mittwoch, den 25.03.2009, 23:23 +0000 schrieb Ciaran McCreesh:
> On Wed, 25 Mar 2009 23:06:37 +0100
> Donnie Berkholz <dberkholz@g.o> wrote:
> > > 9) EAPI 3 bans || ( use? ( ... ) )
> > 
> > What is the suggested replacement? If there's a decent one, sure.
> 
> The replacement is to write the deps out correctly. Every single use of
> || ( use? ( ... ) ) in the tree is wrong.
I created bug #262297 for that (with more text, featuring a citation
from a famous non-gentoo-dev ;-).

> 
> > > 2) EAPI 3 supports slot operator dependencies
> > 
> > Was this for bug #229521? If so, sure.
> 
> Yup. I'm avoiding the term 'multi-slot', though, since that's not what
> this is and we're already using multi- in relation to slots for the
> non-static SLOT idea.
> 
> > > 10) dohard and dosed banned in EAPI 3
> > 
> > I think I missed the reasoning for removing these, particularly
> > dosed. pybugz didn't see any open bugs.
> 
> Portage doesn't merge hardlinks correctly, so dohard is bad.
And there's at least one ebuild in the tree which tries to create a
hardlink across multiple directories and there fails if those are on
separate volumes

>  And
> dosed's been considered deprecated for years.
I've been taught so as well.


> 
> > > 11) doinclude, newinclude for EAPI 3
> > 
> > Is installing to /usr/include by default useful for most packages
> > that want to use this? Or would they /usr/include/${PN}? If you have
> > to change it often, aren't you just as well off using insinto/doins?
> > Should there be an "includeinto"?
> I'd be inclined to agree on that one, but people seem to be after more
> of these do* things.
Would it be possible that doinclude could also strip "+x" from
permission bits? I encountered quiet a few packages having +x set for
whatever reason and I had to change that manually.

> 
> 
> > > 21) REPLACING_VERSIONS and REPLACED_BY_VERSION in EAPI 3
> > 
> > I'm curious why it isn't global. Seems like it would make sense to
> > put it near dependencies. Also I could be wrong, but wouldn't you
> > want to be able to cache this and show smart pretend output, etc?
> 
> I think you're misunderstanding what this is for. It's to allow
> packages to work out whether they're upgrading / downgrading /
> reinstalling / whatever, since Zac broke the devmanual-documented and
> PMS-required way of doing it using has_version and refuses to revert it.
> 
... and this also more or less explains why it's only available in some
phases. What must be said here is that REPLACING_VERSIONS and
REPLACED_BY_VERSION in pkg_pretend and pkg_setup must be used carefully
since they may or may not be defined in those phases and there's also no
way to guarantee it (think of binary packages).