> Yeah, logging is kind of global in nature, I don't see that fundamentally
> changing. The deal with _allowing_ non-global context is to allow something
> like dnf to have a context _they_ control, not so much with having multiple
> different contexts active within rpm at the same time. So I don't see this
> logonce and domain overlapping with that stuff much, if at all really.
It just seems to me like this domain tracking (based on an integer key) tries
to emulate proper OOP encapsulation. IOW, if an object needs a log "context",
it might as well get one, represented as an actual object. The users wanting to
emit messages for that context would then pass the object to the logging
functions, much like we now pass the domain integer.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3417#issuecomment-2449347101
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/3417/c2449347...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
