| 1 |
On Freitag, 13. Juni 2008, Santiago M. Mola wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> As discussed in bug #222721, portage has changed the execution order |
| 5 |
> of phases. It seems the change was introduced in portage-2.1.5 and it |
| 6 |
> makes that, when upgrading a package, pkg_postinst is run after the |
| 7 |
> old version has been removed. This breaks packages which use |
| 8 |
> has_version in pkg_postinst to detect upgrades/downgrades. It can also |
| 9 |
> break packages in more subtle ways. |
| 10 |
> |
| 11 |
|
| 12 |
So someone that has access permissions here: Please do fix the devmanual |
| 13 |
http://devmanual.gentoo.org/ebuild-writing/functions/pkg_postinst/index.html |
| 14 |
|
| 15 |
|
| 16 |
It now states: |
| 17 |
|
| 18 |
Common pkg_postinst Tasks |
| 19 |
The most common use for pkg_postinst is to display post-install informational |
| 20 |
messages or warnings. Note that has_version will operate on the version that |
| 21 |
was installed, which can be useful for selective upgrade messages. |
| 22 |
|
| 23 |
Regards |
| 24 |
Matthias |
| 25 |
-- |
| 26 |
gentoo-dev@l.g.o mailing list |
Archives