[Rpm-maint] [rpm-software-management/rpm] Use full build template (#480)

Jeff Johnson notifications at github.com
Fri Jul 27 15:36:30 UTC 2018


It's hard to reply sanely to someone's half finished pull request that does not have a clearly stated objective.

However I think I can explain why the build scriptlet templaing isn't as useful as one might wish.

The core problem is that %setup and %patch are called "macros" but use an entirely expansion mechanism than all other macros as a result of historical legacy.

The %patch macro was mostly reimplemented, but the equivalent/alternative syntaxes of %patchN and %patch -P N behaviors could not be reproduced sufficiently.

The %setup macro has multiple issues, including sloppy usage (there was never any intent to permit %setup being used multiple times, but that did not stop *ahem* creative packagers), and %setup can take multiple identical options that are L-to-R position sensitive. The macro expansion templating cannot represent multiple identical options that are position sensitive.

The unsolvable issues above, as well as the legacy debt of already created and released spec files whose behavior MUST be preserved exactly, prevented build scriptlet templating from being fully realized.

-- 
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/480#issuecomment-408456284
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180727/6e73f146/attachment.html>


More information about the Rpm-maint mailing list