In configure it's often required to do something along the lines of
`./configure --with-feature=path` for example
`--with-nvml=/usr/local/cuda`
Using %bcond_with mechanism, there doesn't seem to be a way to make this happen
in command line, aside from something like
`rpmbuild -rb --define '_with
This doesn't solve the issue for rpm before 4.18.2 that won't know how to parse
this correctly - basically any EL9 and below won't work correctly with this
approach.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3314#discussionc
I am curious about new feature introduction into SPEC files in that case. SPEC
files are immutable, even between distro versions. A new app packaged has to
consider being built on both EL7 and EL9 while (10 years) over supported
lifetime. Are SPEC files to remain at lowest feature set a decade a
I hear you. The benefit is mostly during development of the SPEC, having to
wait only on -bf as opposed to -bc is quite noticeable during development and
debug, but for the production SPEC I suppose I will drop it.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-so
According to https://rpm-software-management.github.io/rpm/manual/spec.html
some sections are only available from certain versions, for example %conf
(since rpm >= 4.18).
I'd like my SPEC file to use newer capabilities if rpmbuild supports those, and
fallback to older capabilities if built on an
