On Mon, Nov 21, 2016 at 12:21 PM, Emmanuel Charpentier <emanuel.charpent...@gmail.com> wrote: > 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 on sage-support, and especially Dima's answer, as well as this > annoying ticket, discussed in this saga . > > 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... (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 ?
I'm inclined to agree. Add to that all (or at least most) of Sage's other dependencies as well ;) -- 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.
