[Rpm-maint] [rpm-software-management/rpm] spec file preprocessing on rpm level (#1472)

[Michal Novotný]

> A spec will no longer be a spec if such a feature was added. I can see how templating can be useful, but I think this would need to be thought of as a different file type - say, `.spec.in` rather than `.spec` to make it clear.

I think it's mostly matter of preference and compatibility. Additional options (except differentiating file type) that come to mind:
- introduce new spec version, make it possible to declare spec version in spec file by e.g. `# rpmspec:2` in the first line
- bump rpm major version with introduction of this feature
- maybe something else

Having filetype separated seems quite clean to me although it depends on whether rpm would be able to process such templates/files by default and the extension would trigger preprocessing or if an extra switch would be needed (likely cumbersome).


-- 
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/1472#issuecomment-779600475
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20210215/eb23746e/attachment.html>