To clarify: the updated output in this patch was indeed correct, it's just not
an interesting thing to test in this context.
What really changed in commit
https://github.com/rpm-software-management/rpm/commit/aec8bdb53a3013eabf16368e17a65ab69c2136ee
actually makes sense: before the commit %undefine parsed its own argument and
"knew" where to stop as it was not a legit part of a macro name, but this is
not sensical behavior. The argument part in `.%undefine x.` is ambiguous, and
the only way to make it unambiguous is to use %{} as suggested above.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2240#issuecomment-1313661264
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2240/c1313661...@github.com>_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
