[Rpm-maint] [rpm-software-management/rpm] Add %postbuild section / Allow dynamic sub packages (#1239)

[Panu Matilainen]

Been thinking about this on and off, and it still rubs me the wrong way. The spec is a convoluted mess as it is, and even the experienced packagers and macro developers have difficulties understanding and remembering the different time and space contexts of macros and build scriptlets which sit next to each other in the spec. This seems to add yet another time-space dimension to the scene. I'm also finding it difficult to see meaningfulnes of a scriptlet section doing stuff like `"echo Summary: This does foo"` from the spec itself.

For the goal of dynamic sub-packages based on what was built, I still think modelling it after `%files -f <foo>` which every packager already knows would be the way to go. The external file is much easier to understand and troubleshoot for humans (and the computer), the file can be produced by a helper script a'la `%find_lang` from end of `%install`, just think `%find_python` or such instead (and this could be further split to a separate step/hook and automated). It's also not that far off how debuginfo packages come to existence, so it should benefit making those less of a special case too, even if not in direct scope here.

-- 
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/1239#issuecomment-728040854
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20201116/6eca00fa/attachment.html>