Hi,
In a fresh PR I just posted, I want to change our configure script to stop
selecting TLS backend(s) by default and instead "force" the user to make the
decision: this makes all TLS backends "equal" in the eyes of the configure
script and we don't give preference to anyone in particular.
The downside is possibly that if you don't select one, configure doesn't pick
one for you and will instead show an error message - unless you explicitly ask
to build completely without TLS support. The upside is then of course that
there's no surprise to the user what configure will try to use.
As this is a rather big change in approach, I'm keen on hearing what others
think.
The PR: https://github.com/curl/curl/pull/6897
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
