[Rpm-maint] [rpm-software-management/rpm] Changes to transaction file triggers to make them viable for systemd (Discussion #4016)

[Panu Matilainen]

@DaanDeMeyer wrote:
> Is there anything I can do to help this get prioritized? The more I look at this the more I realize how broken the current macros are when it comes to stopping units that are getting removed. I would hate to have to come up with some horrifying hack to deal with this on our end.

This is a priority, but we have preciously little capacity available, especially so for this quarter due to RHEL-side commitments.

We should be able to take a closer look on Q1/26, but what we can actually do about it is another question. We should be able to address some paper cuts that have been identified, but we wont be able to do a grand redesign of the whole file trigger system. So it all depends on how much is achievable by smaller adjustments.

The duplicate scripts running seems like one such obvious thing. The other one that I've been thinking about is that behavior of considering already installed files in (transaction) file triggers. It seems to me the DWIM semantics of that would be: only include installed files in file triggers on initial install of the trigger owner, and final removal. In all other cases, only trigger on files in the transaction. It's quite a change of semantics, but I don't think the current semantics are particularly meaningful for folks implementing triggers.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/4016#discussioncomment-14878033
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/4016/comments/14878033 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20251105/eb4cc328/attachment-0001.htm>