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.
What I'll be looking into now is:
- `BuildSystem:` a singleton tag to declare the used build system for the
package (tag name open to speculation still, `Build` is kinda tempting too)
- `BuildOption(section):` a repeatable tag to declare options one by one to
pass to the build system for a given section
- `BuildOption:` without parentheses is equal to `BuildOption(conf)` which is
by far the most common place needing options
Support for a buildsystem is implemented by filling in the necessary macros for
these sections. Said macros are responsible for passing the options from the
BuildOption tags to the buildsystem as appropriate.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1087#issuecomment-1794476191
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/1087/1794476...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
