On Fri, Nov 9, 2018 at 2:38 PM Emmanuel Charpentier <emanuel.charpent...@gmail.com> wrote: > > > > Le vendredi 9 novembre 2018 13:40:12 UTC+1, Erik Bray a écrit : >> >> Can someone remind me again why SSL libs aren't provided by the system >> on macOS, and/or why those libs can't be used for building Python's >> ssl module? > > > From the current installation guide : > ===================== Begin quote ===================== > Some Sage components (and among them, most notably, Python) “use the OpenSSL > library for added performance if made available by the operating system” > (literal quote from the Python license). Testing has proved that : > > Sage can be successfully built against other SSL libraries (at least GnuTLS). > Sage’s -pip facility (used to install some Sage packages) is disabled when > Sage is compiled against those libraries. > > Furthermore, the Sage license mention that the hashlib library (used in Sage) > uses OpenSSL. > > Therefore, the OpenSSL library is recommended. However, Sage’s license seems > to clash with OpenSSL license, which makes the distribution of OpenSSL along > with Sage sources dubious.
I don't think that's true. OpenSSL is not distributed "along with Sage sources". At most, instructions for installing OpenSSL are. This goes for any dependency of Sage that has an SPKG. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
