A fair question, which even occurred to me while I was typing the previous. Thinking about it more, we aren’t really ‘reliant’ on the non TLS version (in a ‘production’ sense) it just makes our lives easier for various reasons to be able to build common components in some environments where we don’t (or don’t ‘yet’) have the GSKit integration available.
So not a strong argument for retaining the facility to build without TLS, though we’d be mildly sad to lose it (and maybe it would affect other users in similar ‘process rather than technical’ ways). Anthony Beardsmore IBM MQ Development IBM UK --------------------------------------------- abea...@uk.ibm.com<mailto:abea...@uk.ibm.com> -- From: Daniel Stenberg <dan...@haxx.se> Date: Monday, 13 January 2025 at 12:32 To: Anthony Beardsmore <abea...@uk.ibm.com> Cc: libcurl development <curl-library@lists.haxx.se>, Calvin Buckley <cal...@cmpct.info> Subject: [EXTERNAL] Re: curl and IBM GSKit (re: Does anyone build curl or libcurl without TLS support?) On Mon, 13 Jan 2025, Anthony Beardsmore wrote: > To come back to the topic of this thread, we are also therefore to an extent > reliant on the ‘no TLS’ options remaining clean. This triggered my curiosity! How so? Why do you need to build without TLS cleanly in order to have a working TLS backend patched in? Or what did I misunderstand? -- / daniel.haxx.se || https://rock-solid.curl.dev Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
