diff options
author | Zac Medico <zmedico@gentoo.org> | 2008-06-17 05:44:21 +0000 |
---|---|---|
committer | Zac Medico <zmedico@gentoo.org> | 2008-06-17 05:44:21 +0000 |
commit | dbd7ea472258ed45bcd4ad5b837f7103afd02f6e (patch) | |
tree | 2094f2c3b13f36a77a83afea34795858d329a2c2 | |
parent | 30bcd77ebf8d111ec6ac496115f871f55893e683 (diff) | |
download | portage-dbd7ea472258ed45bcd4ad5b837f7103afd02f6e.tar.gz portage-dbd7ea472258ed45bcd4ad5b837f7103afd02f6e.tar.bz2 portage-dbd7ea472258ed45bcd4ad5b837f7103afd02f6e.zip |
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
-rw-r--r-- | doc/package/ebuild/phases.docbook | 57 |
1 files changed, 57 insertions, 0 deletions
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 @@ </listitem> </itemizedlist> </para> + <sect2 id='package-ebuild-phases-previous-installed'> + <title>Interaction with previous installed version</title> + <para> + The order for upgrade and downgrade operations changed in + version 2.1.5, but the order for reinstall operations remained unchanged. + </para> + <sect3 id='package-ebuild-phases-before-2.1.5'> + <title>Upgrade/downgrade order used by versions less than 2.1.5 (deprecated)</title> + <para> + <itemizedlist> + <listitem> + pkg_preinst + </listitem> + <listitem> + pkg_postinst + </listitem> + <listitem> + pkg_prerm + </listitem> + <listitem> + pkg_postrm + </listitem> + </itemizedlist> + </para> + </sect3> + <sect3 id='package-ebuild-phases-after-2.1.5'> + <title>Upgrade/downgrade order starting with version 2.1.5</title> + <para> + The new order for upgrades and downgrades is identical to the order used + for reinstall operations: + </para> + <para> + <itemizedlist> + <listitem> + pkg_preinst + </listitem> + <listitem> + pkg_prerm + </listitem> + <listitem> + pkg_postrm + </listitem> + <listitem> + pkg_postinst + </listitem> + </itemizedlist> + </para> + <para> + 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. + </para> + </sect3> + </sect2> </sect1> |