On Fri, 13 Jun 2008 21:55:29 +0200
"Santiago M. Mola" <coldwind@g.o> wrote:
> As discussed in bug #222721, portage has changed the execution order
> of phases. It seems the change was introduced in portage-2.1.5 and it
> makes that, when upgrading a package, pkg_postinst is run after the
> old version has been removed. This breaks packages which use
> has_version in pkg_postinst to detect upgrades/downgrades. It can also
> break packages in more subtle ways.

Given that the number of affected ebuilds is so high, I'd say Portage
should have to revert the changes...

This is an EAPI scope change, if anything. Although even then the
implications are a bit messy since you're talking the interaction of
two different EAPIs.

-- 
Ciaran McCreesh