From: Zac Medico Date: Tue, 17 Jun 2008 05:44:21 +0000 (-0000) Subject: Add a "Interaction with previous installed version" section to document the X-Git-Tag: v2.2_rc1~24 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=dbd7ea472258ed45bcd4ad5b837f7103afd02f6e;p=portage.git Add a "Interaction with previous installed version" section to document the upgrade/downgrade phase execution order change from bug #226505. svn path=/main/trunk/; revision=10683 --- diff --git a/doc/package/ebuild/phases.docbook b/doc/package/ebuild/phases.docbook index 5c7f04969..383c605ce 100644 --- a/doc/package/ebuild/phases.docbook +++ b/doc/package/ebuild/phases.docbook @@ -40,4 +40,61 @@ + + Interaction with previous installed version + + The order for upgrade and downgrade operations changed in + version 2.1.5, but the order for reinstall operations remained unchanged. + + + Upgrade/downgrade order used by versions less than 2.1.5 (deprecated) + + + + pkg_preinst + + + pkg_postinst + + + pkg_prerm + + + pkg_postrm + + + + + + Upgrade/downgrade order starting with version 2.1.5 + + The new order for upgrades and downgrades is identical to the order used + for reinstall operations: + + + + + pkg_preinst + + + pkg_prerm + + + pkg_postrm + + + pkg_postinst + + + + + Now that pkg_postinst is called after all other phases, it's not possible to + call has_version in pkg_postinst to detect whether the current install + operation is an upgrade or downgrade. If this information is needed during the + pkg_postinst phase, do the has_version call in an earlier phase (such as + pkg_preinst) and store the result in a global variable to be accessed by + pkg_postinst when it is called. + + +