Vít Ondruch wrote on Thu, May 16, 2019 at 08:28:45AM +0200:
>> This was removed on my request, triggered by this PR .
>> concur that this should happen just in Rawhide and never be backported
>> into stable releases.
> I don't see why this is a problem. Removing an unneeded build
> dependency from a package shouldn't affect anything else. That it did
> merely pointed out a bug in the other package where the build deps
> were incomplete.
The problem is not the build dependency, you can get rid of it
everywhere without any impact except for openssl itself.
What is less transparent is the removal of an actual Require (two
actually, zlib-devel is no longer pulled either) ; that can impact other
packages and workflows.
Someone installing openssl-devel could have expected it to pull
krb5-devel and zlib-devel, now they need to install it explicitely
separately for their own use as well, it's a change in user interface.
We lived with this "bug" for years. There is no reason to
fix this bug
in stable release just to cause other bugs. And it was obvious it would
broke at least build of Ruby and now it is obvious it did broke not just
Ruby. It would be enough to have to solve this issues in Rawhide.
Also, (not) pulling -devel package into build root might result in some
subtle bugs such as some part of package functionality disabled based on
build configuration, which might went unnoticed, until the package is
released. This is irresponsible.
configure with feature autodetection is a PITA :/