summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjbj <devnull@localhost>1999-08-20 19:11:37 +0000
committerjbj <devnull@localhost>1999-08-20 19:11:37 +0000
commit75808ee2d4c1b34c70758d5c72a2b7a386b1124b (patch)
tree42c09c9b2003532d6a550685862012c0e2d0c61d /doc
parente42968ff8b28a632917ec526bae27b10d8e5576f (diff)
downloadlibrpm-tizen-75808ee2d4c1b34c70758d5c72a2b7a386b1124b.tar.gz
librpm-tizen-75808ee2d4c1b34c70758d5c72a2b7a386b1124b.tar.bz2
librpm-tizen-75808ee2d4c1b34c70758d5c72a2b7a386b1124b.zip
Add script execution order.
CVS patchset: 3242 CVS date: 1999/08/20 19:11:37
Diffstat (limited to 'doc')
-rw-r--r--doc/manual/triggers24
1 files changed, 24 insertions, 0 deletions
diff --git a/doc/manual/triggers b/doc/manual/triggers
index c148f1bca..40f90316d 100644
--- a/doc/manual/triggers
+++ b/doc/manual/triggers
@@ -122,3 +122,27 @@ never be run when the package containing the trigger is removed.
While this type of trigger is almost never usefull, they allow a package to
fix errors introduced by the %postun of another package (or by an earlier
version of that package).
+
+Order of Script Execution
+-------------------------
+
+For reference, here's the order in which scripts are executed on a single
+package upgrade:
+
+ new-%pre for new version of package being installed
+ ... (all new files are installed)
+ new-%post for new version of package being installed
+
+ any-%triggerin (%triggerin from other packages set off by new install)
+ new-%triggerin
+ old-%triggerun
+ any-%triggerun (%triggerun from other packages set off by old uninstall)
+
+ old-%preun for old version of package being removed
+ ... (all old files are removed)
+ old-%postun for old version of package being removed
+
+ old-%triggerpostun
+ any-%triggerpostun (%triggerpostun from other packages set off by old un
+ install)
+