To recoup the very useful discussion and ideas from the now withdrawn draft PR:
To make things properly declarative, overriding sections should not be a part
of the plan at all. Instead there should be a way to declare independent build
options one by one. And the "auto" in the name needs to go.
The above specification is now implemented in #2774, more or less.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1087#issuecomment-1820808980
You are receiving this because you are subscribed to this thread.
Message ID: __
Closed #1087 as completed via f02ddfd121d91ea00a534a0e04374c478f56d437.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1087#event-11487059627
You are receiving this because you are subscribed to this thread.
Message ID:
__
Found out about this new feature. How does one go about constructing such
`BuildSystem`, do they just define a `%buildsystem__conf` macros?
I am considering the case of [MPI
packaging](https://pagure.io/packaging-committee/issue/1345) and it would be a
neat approach to `for` looping all mpi var
It's documented here:
https://rpm-software-management.github.io/rpm/manual/buildsystem.html#supporting-new-build-systems
But closed tickets are not a good place for questions, please open a new thread
in https://github.com/rpm-software-management/rpm/discussions
--
Reply to this email directl