| 1 |
On Fri, 13 Jun 2008 21:55:29 +0200 |
| 2 |
"Santiago M. Mola" <coldwind@g.o> wrote: |
| 3 |
> As discussed in bug #222721, portage has changed the execution order |
| 4 |
> of phases. It seems the change was introduced in portage-2.1.5 and it |
| 5 |
> makes that, when upgrading a package, pkg_postinst is run after the |
| 6 |
> old version has been removed. This breaks packages which use |
| 7 |
> has_version in pkg_postinst to detect upgrades/downgrades. It can also |
| 8 |
> break packages in more subtle ways. |
| 9 |
|
| 10 |
Given that the number of affected ebuilds is so high, I'd say Portage |
| 11 |
should have to revert the changes... |
| 12 |
|
| 13 |
This is an EAPI scope change, if anything. Although even then the |
| 14 |
implications are a bit messy since you're talking the interaction of |
| 15 |
two different EAPIs. |
| 16 |
|
| 17 |
-- |
| 18 |
Ciaran McCreesh |
Archives