dnf/SOURCES/0008-doc-Describe-a-behavior-when-plugin-is-removed-RhBug1700741.patch
2021-09-10 09:03:20 +00:00

34 lines
1.3 KiB
Diff

From c638887211b3d9c0b3b1fcb6eb6b62f384d2c263 Mon Sep 17 00:00:00 2001
From: Jaroslav Mracek <jmracek@redhat.com>
Date: Mon, 22 Jul 2019 09:29:42 +0200
Subject: [PATCH] [doc] Describe a behavior when plugin is removed (RhBug:1700741)
When plugin is removed or obsoleted all hooks of removed plugins after
transaction are skipped. The behavior was added because some
of dependencies of the plugin could be also removed and unavailable in
memory. We apply the same behavior also for obsoleted plugins, because
we suggest that obsoleting plugin could have a different code base.
The behavior is not applicable for downgrades or upgrades.
https://bugzilla.redhat.com/show_bug.cgi?id=1700741
---
doc/api_plugins.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/api_plugins.rst b/doc/api_plugins.rst
index f5d9829..5015e42 100644
--- a/doc/api_plugins.rst
+++ b/doc/api_plugins.rst
@@ -62,6 +62,7 @@ When DNF CLI runs it loads the plugins found in the paths during the CLI's initi
.. method:: transaction
Plugin can override this. This hook is called immediately after a successful transaction.
+ Plugins that were removed or obsoleted by the transaction will not run the transaction hook.
You may want to see the comparison with `yum plugin hook API`_.
--
libgit2 0.28.2