On Fri, Nov 6, 2020 at 12:08 PM Daniel Gustafsson <dan...@yesql.se> wrote: > > > On 6 Nov 2020, at 00:36, Michael Paquier <mich...@paquier.xyz> wrote: > > > I still don't see the point of this extra complexity, as > > USE_OPENSSL_RANDOM implies USE_OPENSSL, > > As long as we're sure that we'll remember to fix this when that assumption no > longer holds (intentional or unintentional) then it's fine to skip and instead > be defensive in documentation rather than code.
I think the defensive-in-code instead of defensive-in-docs is a really strong argument, so I have pushed it as such. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
