Hi, <useless rant>
We've been down this road before with Sage, and it's pretty annoying. I've personally wasted hundreds of hours on it (GNUtls, openssl, etc.) Programmers playing lawyers have ended up with a broken and inconsistent legal foundation. There is no easy way out, since only copyright owners can change licenses. Because this is volunteer open source, much of the generation that got us into this mess is MIA (or even dead in some cases). Sigh... </useless rant> -- William On Thu, Oct 27, 2016 at 8:18 AM, Emmanuel Charpentier <emanuel.charpent...@gmail.com> wrote: > > > Le jeudi 27 octobre 2016 17:00:05 UTC+2, Jean-Pierre Flori a écrit : >> >> >> >> On Thursday, October 27, 2016 at 4:59:02 PM UTC+2, Jean-Pierre Flori >> wrote: >>> >>> >>> >>> On Thursday, October 27, 2016 at 4:49:23 PM UTC+2, Emmanuel Charpentier >>> wrote: >>>> >>>> >>>> >>>> Le jeudi 27 octobre 2016 16:04:52 UTC+2, Jean-Pierre Flori a écrit : >>>>> >>>>> >>>>> >>>>> On Thursday, October 27, 2016 at 3:59:26 PM UTC+2, Emmanuel Charpentier >>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> Le jeudi 27 octobre 2016 13:10:17 UTC+2, François a écrit : >>>>>>> >>>>>>> It is a most interesting point because it explain why >>>>>>> the R binary installed from epel for RH7.1 and family >>>>>>> isn’t linked to openssl. >>>>>> >>>>>> >>>>>> How old is RH7.1 ? The introduction of the libcurl requirement dates >>>>>> from the R 3.3.0 release, (May 3, 2016). >>>>>> >>>>>> I note that Debian (notoriously twitchy about license issues) didn't >>>>>> seem to have any qualms packaging 3.3.0, nor 3.3.1. >>>>> >>>>> >>>>> I'd say Debian links curl to GnuTLS. >>>> >>>> >>>> Probably not : My system's curl-config --protocols says that HTTPS: is >>>> supported. A trial of curl's configure --without-ssl --with-gnutls does not >>>> claim to support it (in the summary printed at th end of ./configure...). >>>> >>> Are you sure you installed the gnutls dev headers? >>> GnuTLS provides an SSL implem, not just SSL. >>> >>>> >>>> However, I'm not sure : Debian's blurb about libcurl3-gnutls says that >>>> it supports https, imaps, ldaps, smtps and pop3s. >>>> >>>> To be sure, I'll have to setup a virtual machine with a minimal >>>> environment (no openssl, of course) and try to setup libcurl (and, if >>>> successful, Sage) in that environment. This is time consuming, so not quite >>>> real soon... >>> >>> You mean with gnutls? >>> Or with no ssl/tls at all? >>> >>> I already did the latter and it works (modulo hacking R's configure). >> >> >> (sage-sh) jpflori@gcc1-power7:sage.git$ curl-config --protocols >> DICT >> FILE >> FTP >> GOPHER >> HTTP >> IMAP >> POP3 >> RTSP >> SCP >> SFTP >> SMTP >> TELNET >> TFTP >> (sage-sh) jpflori@gcc1-power7:sage.git$ R --version >> R version 3.3.1 (2016-06-21) -- "Bug in Your Hair" >> Copyright (C) 2016 The R Foundation for Statistical Computing >> Platform: powerpc64-unknown-linux-gnu (64-bit) >> >> R is free software and comes with ABSOLUTELY NO WARRANTY. >> You are welcome to redistribute it under the terms of the >> GNU General Public License versions 2 or 3. >> For more information about these matters see >> http://www.gnu.org/licenses/. > > > No HTTPS. Damn.. > > -- > 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. -- William (http://wstein.org) -- 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.
