recs is not really suited for this. It is a vector so lookups are not cheap. It
only stores WARNING and above. We might want to link to the recs entry but even
that does not really solve anything if the lower prio entries are missing.
The additional string is there for cases where the message contains differing
info. E.g. the package name or location of the error. Imagine suppressing a
missing macro message. This will give a file and line number. And you do want
that so you can look at the place where things go wrong in case it is just a
typo. You still want to suppress the follow up messages if the macro is
actually missing. So having a key allows to put them all under the same
category.
I don't think we will have logging objects for every possible occasion but only
for majors things like builds or transactions. So I expect the domain to stay
relevant even if we no longer have global logging. But that might just me being
unimaginative.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3417#issuecomment-2449257525
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/3417/c2449257...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
