|x| Yes, we should fully support OpenSSL now, and clarify the licensing issue.
Where I want to add that my support is conditional on that this can be done in a legal way. On Monday, 16 October 2017 11:47:09 UTC+2, Emmanuel Charpentier wrote: > > Following numerous discussions on this list an various tickets, the issue > of maintaining Sage-specific patches to various components of Sage emerged > again about the proposed upgrade <https://trac.sagemath.org/ticket/24026> > of R to 3.4.2 (discussed here > <https://groups.google.com/forum/#!topic/sage-devel/rhMrNK_2c24>). > > Since Trac#22189 <https://trac.sagemath.org/ticket/22189>, installation > of a systemwide opennssl is recommended (may be too strongly > <https://trac.sagemath.org/ticket/22620>, in the taste of some > respectable Sage developers...). > > The proposed inclusion would entail : > Deprecation of our OpenSSL-avidance patches > Sta > At compilation, research of a systemwide OpenSSL > If found : do nothing > > -- 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.
