Also, note that even in >= 4.14, macros (not variables) do have a scope: inside
parametric macros, all %defines are local.
--
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/issues
We had this up to rpm 4.14 (all macros being local to the surrounding %{}
scope), and the only thing it did was create endless confusion. Okay, buggy
implementation didn't help, but there's no way we're going back to that mess.
Remember the "%define is evil, everybody must use %global" touting i
Right now a lot of things need special tags in rpm just because they have a
specific (usual subpackage) scope, and can be declared in multiple scopes
Please add a generic construct to specify the scope of a set of variable, so
those special Tag constructs can be ultimately replaced by easy to ma
