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 in Fedora?
That's where it comes from:
```%{?python_sitearch: %define python_sitearch %(%{__python} -c "from
distutils.sysconfig import get_python_lib; print get_python_lib(1)")}```
I have been entertaining a *voluntary* local scope for macros though, quite
simply `%local` as opposed to `%global`. This would be more in spirit of keep
simple things simple and complicated things possible.
--
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/1150#issuecomment-607055121
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
