Le mercredi 18 octobre 2017 15:37:13 UTC+2, Dr. David Kirkby (Kirkby Microwave Ltd) a écrit : > > On 18 October 2017 at 14:13, Erik Bray <erik....@gmail.com <javascript:>> > wrote: > >> On Wed, Oct 18, 2017 at 11:52 AM, Dr. David Kirkby (Kirkby Microwave >> Note: We're not talking about adding *any* OpenSSL code to SageMath. >> Sage would never be distributed with code from OpenSSL. We're only >> talking about providing a means to download and install it from >> source, and about shipping binaries that includes it. >> >> > How exactly do you intend shipping binaries that include the OpenSSL > library, while not including *any* OpenSSL code? >
Simple : the same way that e. g. the Cygwin port ships code interacting with, say, Windows without *including* *any* Windows code... : by using published APIs to published libraries. We do not have to include OpenSSL *code* to use OpenSSL as long as OpenSSL is installed somewhere reachable by Sage. The contentious point is : how do we ensure that OpenSSL *is* installed ? With most packages, we include it, by posting it on the Sage servers and fetching if necessary. This, in some eyes, is "including" code, since we post a copy on our servers. To these (respectable) people, this is "legally" dubious (in which legislation(s), BTW ???), until the OpenSSL license changes. We need at least an interm solution. - Depending on a systemwide SSL is a possibility. - If we retain the option "Include now", other possibilities could be discussed. -- Emmanuel Charpentier > > Dave > -- 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.
