Let's look at the bigger picture here a bit, because #3336 is an isolated
use-case and rather unusual at that so it's actually not that interesting in
itself. The typical case of log suppression we'd want is of the "last message
repeated 123 times" kind rather than silence *all* the following messages.
We have at least the following cases with different needs wrt lifetime:
1) per transaction
2) per package in transaction
3) spec parse (optionally followed by package build)
4) process lifetime
1-2 and 3 are kinda separate groups and typically don't exist within the same
process. I'm quite sure we technically have stuff that would qualify for 1)
besides #3336, and 4) is all we have at the moment.
I see two ways to think about #3336: either its about unknown key tracking with
specific semantics, or its just a warning message with a particular
implementation. In the latter case we could just replace the existing behavior
of unknown key tracking with the "last warning repeated 123 times" that the
rest of the log suppression wants. I don't know if we have anything else that
has the same semantics as the current unknown key warning - maybe we do, I just
don't remember any atm.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3395#issuecomment-2443807770
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3395/2443807...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
