Dear list, The fact that we can't ship openSSL (see uncountable theads in sage-devel and others) seems to pose more and more difficulties. See for example this thread <https://groups.google.com/forum/#!topic/sage-support/rDV9uGT2ViM> on sage-support, and especially Dima's answer <https://groups.google.com/d/msg/sage-support/rDV9uGT2ViM/GuKDbhSKAwAJ>, as well as this annoying ticket <https://trac.sagemath.org/ticket/21767>, discussed in this saga <https://groups.google.com/forum/#!topic/sage-devel/QaBdHSNJuKg> .
Could'nt we add OpenSSL as a prerequisite to Sage, and it"s development files as a prerequisite to building Sage ? This would require of the user to install OpenSSL systemwide, thus making it "system software" and satisfying the strange licensing requirements that bother us. One could even do that indirectly, by requiring a systemwide libcurl supporting https : this would de facto enforce the systemwide installation of OpenSSL (or a reasonable facsimile). That's what I was trying to do in this proposal <https://trac.sagemath.org/ticket/21767#comment:41>... (IIRC, the problem with libcurl is also bound to OpenSSL : libcurl itself is not a problem. But I'll have to check : if this is true, we can require OpenSSL and ship libcurl which will then compile cleanly). Comments ? Especially wrt Macs, which seem to be further encumbered by Apple's dirty tricks... Should we have a vote ? -- Emmanuel Charpentier -- 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.
