rpmbuild now seems to use builtin generation of requires (& provides).
This silently breaks .spec files that attempt to modify the requires generation
by changing __find_requires.
It would be nice if this breakage was not silent. Something like:
if __find_requires is changed and _use_internal_dependency_generator != 0 then
print a warning message.
Alternatively, maybe overriding __find_requires could automagically turn off the
BTW there are some packages in severn that have been bitten by this (e.g.,
libao). Not sure how many.
I disagree. %__find_requires needs to be removed entirely, will
happen at my earliest opportunity.
Curious as to why you are thinking of removing __find_requires. we use this
often on custom rpms to filter out bogus deps. an Example:
the RPM includes samples or example or contrib binaruies that require lots of
extra packages to run but the core/real parts of the RPM itself run just fine
without the other packages. so if we can't filter out these "bogus" deps then
we would have to install using --nodeps which is not a good thing in my mind.
or is there some other option?
which setting _use_internal_dependency_generator to 0 fixed things for me.