Le mercredi 25 octobre 2017 21:37:59 UTC+2, Michael Orlitzky a écrit : > > On 10/25/2017 12:14 PM, Emmanuel Charpentier wrote: > > Can you explain how the Wget case is different from ours ? > > A single entity (the FSF) owned the copyright on all of the code in wget > when they changed the license to add the exception. The same is not true > of SageMath: we don't have copyright assignment, and we bundle a lot of > code that is copyrighted by complete strangers. >
Okay : I'm not still convinced, but I'll follow you on a "primum non nocere" basis. If we follow you, we have to take back any talk of *inclusion* right now. The solution is to depend *unconditionally* on a systemwide OpenSSL and stop building if not found, possibly hinting at steps to that effect. *After* OpenSSL relicensing, we can introduce a standard openssl package, whith no huffing and puffing. Now, all that I miss is a hint to give to people wanting to build sage *withut* OpenSSL. Since we get rid oif the current anti-OpenSSL patches, We ncan't let these users hang dry... -- Emmanuel Charpentier -- 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.
