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

[Jeff Johnson]

Re: "... no progress in unifying dialects ..."

We are discussing macro templating through recursive string substitution that was implemented in 1998 and abstracted into its current form in 1999. Macros of any sort were seldom used in Red Hat packaging, even modest adoption took 5-6 years. And there are still insanities like "exit 0" that remain uncorrected today, as well as common de facto practice of patching rpm's own macro configuration file in spite of the warning at the top of the file.

You tell me what progress means: compared to, say, sedimentary rock formation, rpm development might appear to make progress at the speed of light.

Templating is definitely a powerful concept when done correctly. Less interesting is using spec file recipes as a form of markup to drive a build, spec files are too quirky and idiosyncratic, there are multiple better forms of build markup around these days, including Gentoo, ant for Java and more, *BSD ports, and bitbake, to name just a few examples that I consider better markup for implementing recipes that drive a build.

-- 
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-408625465
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180728/75b81b90/attachment.html>