Replies: 3 comments
-
The examples make me wonder if there's some confusion with %bcond involved. Anyway, it's an interesting suggestion. A problem with the section syntax is that BuildOptions can exist for multiple sections, so you'd need potentially multiple sections too, something like And yes, BuildOption is not exactly pretty (the spec syntax doesn't easily lend itself to aesthetics 😆 ). It's all about declarativity, and the benefits coming from that. |
Beta Was this translation helpful? Give feedback.
-
I believe our prototype build system simply reads all the BuildOptions and generates |
Beta Was this translation helpful? Give feedback.
-
Um. BuildOption's are something only rpmbuild has access to, and passes them to the specified section as appropriate. |
Beta Was this translation helpful? Give feedback.
-
Following on this feature: https://rpm-software-management.github.io/rpm/manual/buildsystem.html
We would like to adopt it for the Fedora Java stack. This means replacing a lot imperative code like:
with
%BuildOption
-s.However in practice what it would mean for us is that it would now look like:
And I say that this is hardly an improvement when it comes to readability.
I imagine there could be a
.spec
section%buildoptions
where I could write line-separated options, like:Beta Was this translation helpful? Give feedback.
All reactions