FWIW, I think that deprecation+eventual removal is the way to go in this case.
If the macro was exposed, but not *actually used*, it'd be OK to quickly yank
it out. But clearly it is in use, and we know that the removal breaks packages
that are out there. I appreciate the desire to make a clean break, but rpm is a
foundational package that needs to preserve backwards compatibility.
--
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/pull/1668#issuecomment-832570517
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
