Documentation says "for all installed packages that contained...", nowhere does
it say installed in *this* transaction.
The "obvious" reason(s) for the behavior is that when installing the package
containing the trigger, you want to get it to do its thing on the packages that
are already installed. And when the file containing the trigger is erased,
it'll undo it's thing. On upgrades of the package containing the trigger you'd
want to rerun the script because it might contain fixes / new behaviors that
the old one did not.
--
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/issues/386#issuecomment-365197422
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
