Overview
Request 783547 accepted
No description set
- Created by scarabeus_iv
- In state accepted
Loading...
Request History
scarabeus_iv created request
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:69"
staging-bot accepted review
Picked "openSUSE:Factory:Staging:adi:69"
dimstar accepted review
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:adi:69 got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:adi:69 got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:adi:69 got accepted.
Is any package using boringssl as a dependency right now? Hopefully not. I totally forgot about that package and I would be happy to totally nuke it if nobody is against. :)
Envoy uses OpenSSL now. And Chromium has BoringSSL sources included (which come from different branch anyway). So I see no reason for maintaining it and putting an effort to fix different architectures.
I think tensorflow and few minimal others use the boringssl sadly. I would like to have only our suse openssl as it is much more secure to have just one ssl impl. tho.
I see. That's unfortunate. Although in case of tensorflow, I see that it still uses bundled sources of boringssl instead of this package. https://build.opensuse.org/package/view_file/science:machinelearning/tensorflow/tensorflow.spec - line 185
And tensorflow should be compatible with OpenSSL already (building with
TF_SYSTEM_LIBS="boringssl"
should do the job). I will try to do that in our package.