One issue with curl is that you sooner or later will need the root certificates to use it, namely when you start downloading from a https site. E.g. in hashstack I recently added the root certs:
https://github.com/hashdist/hashstack/issues/969 This issue already faces us with openssl but since we actually don't use it much we could avoid it so far. But when replacing curl in the PATH we are going to run into that issue. I would be happy with adding curl (and up-to-date root certificates) to the list of system requirements for building Sage and avoid that can of worms. PS: and no, you can't use the OS-provided certs, since Apple had to cook their own sauce once more. On Monday, October 24, 2016 at 6:09:24 AM UTC-4, Emmanuel Charpentier wrote: > > It looks like curl <https://curl.haxx.se/>, which was formerly installed > by R installation, must now be installed > <https://cran.r-project.org/doc/manuals/R-admin.html#Essential-programs-and-libraries> > > in order to install R. > > One can note that a problem will rarely exists, since most Sage users have > curl installed in their system. However, a user having only sage installed > (e. g. Sage's virtual machine for Windows) will see it... > > If we want to keep R a standard package, we have to either > > - patch R and add curl's installation (heavy : the R core Team threw > the towel on it), > - add curl to Sage's prerequisites (lighter to us, but still heavy to > the users), > - or make it a standard package, on which R must depend. > > > The latter solution has my reference(much simpler). > > What is yours ? > > -- > 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.
