Causing a full stop failure during expansion raises expectations to provide
better RPM error messages, or behave more gracefully.
The expectations often cannot be met because macro expansion is context free
(by design).
Debugging a macro expansion that is exiting is often harder than printing
whatever and continuing a package build. There are simply too many ways for
templated macro expansions to go off the rails for %error to be really useful.
--
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/commit/94e8cd6058cba07b5b97785d2cc91566ec267eaf#commitcomment-23700566
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
