[Rpm-maint] [rpm-software-management/rpm] Implement a transaction set change notification callback (#1367)

[Panu Matilainen]

Thanks for the feedback!

> The question is, who triggers this scriptlet? Dependency between scriptlets? It was a simple example. However, for a bigger transaction with multiple packages, the question is: Why the scriptlet from installed package XY was started? Perhaps this is seen in the chronological order of callbacks.

File triggers may be triggered by arbitrary number of packages, this is not communicated outside rpm internals in any way because it's irrelevant and unwieldy (think glibc ldconfig - every single package with a shared library installation will trigger it, now think of multiple such triggers in the same transaction, which is what you're seeing above). 

Scriptlet execution wrt callbacks follows a simple rule: scriptlets always execute in the context of the package owning the scriptlet, regardless of whether that package is otherwise part of the transaction or not. So the rpmte (or header in the old style callback) is where the executing scriptlet came from.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1367#issuecomment-698760631
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20200925/540d6c8b/attachment.html>