[Rpm-maint] [rpm-software-management/rpm] RFE/RFC add support for %{yaml: } (#583)

nim-nim notifications at github.com
Wed Oct 31 09:39:33 UTC 2018


I'm not sure rpm specs are shell oriented or not, the scriplets parts, sure, the header/variable parts look more evolved custom config that any specific way to do it to me.

And I have no problem with the scripts parts, they work well and are efficient, I don't see the point of changing them.

What I don't like at all is the variable/Tags/metadata declarations where one is always hitting quirks and idiosyncrasies and badly defined behaviour and misplaced rpm assertions:
 * global vs define
 * Tag vs variable

Those differences and stupid quirks exist only because the rpm custom variable syntax makes no provision for structure, and you need structure to express scoping, so structure was bolted on (badly) via lots of implicit rules and naming workarounds. With lots of asserts to try to glue it all together and prevent the kludge pile from falling apart.

So no, I'm definitely **not** asking for a new  spec-wide input build recipe format, I'm asking for an alternative clean and regular way to express variables and their scope. Optional way that can be mixed and matched with existing syntax like lua has been progressively added to specs, **not** big-bang change everything rpm5-style changes.

Yaml was invented to express structured variable lists, and ansible shows it can be mixed cleanly with shell code when you are careful to use the yaml part for variables only.

-- 
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/583#issuecomment-434621511
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20181031/9721439d/attachment-0001.html>


More information about the Rpm-maint mailing list