It is all rather rigid at the moment, I agree. I'd also say there's probably an
underlying assumption that the build options are for the project being built,
rather than the buildsystem (except %prep which seems more ambiguous), and so
these kind of things don't seem to fit in.
For now I suppose something like this would be have to be done with "master"
macros that dispatch and do any necessary transforms for calling further
sub-components. As you basically mention there - possible but tedious.
Making the parsed buildoptions available to Lua should be well within the realm
of possibilities and something I wanted to do anyhow, just didn't make it to
"version 1.0". And once we have that, it shouldn't be such a long step to allow
for custom entries. It needs a somewhat different syntax though because the
"argument" to BuildOption is strictly a section name.
On a related note: one entirely untapped source of opportunities is arguments
to the buildsystem macros themselves, that are required to be parametric but
there's no way to pass options to. I don't have any concrete plans for those,
ie whether these would be something like global options common to all
buildsystems or something else (probably the latter).
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3689#discussioncomment-12686969
You are receiving this because you are subscribed to this thread.
Message ID:
<rpm-software-management/rpm/repo-discussions/3689/comments/12686...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
https://lists.rpm.org/mailman/listinfo/rpm-maint
