On 20 Mrz., 18:05, John Cremona <john.crem...@gmail.com> wrote: > On 20 March 2012 16:39, leif <not.rea...@online.de> wrote: > > I thought HTTPS (which requires SSL of course) wasn't strictly needed > > in Sage, but since it is omnipresent (many Python packages use it), it > > doesn't make sense to not have it. I.e., people frequently happen to > > notice they don't have _ssl *after* they've built Sage's Python > > package without SSL support. > > Indeed: every time I build my working copy of Sage (not counting test > version here) I have to do first sage -i openssl and then sage -f > python to rebuild python. Otherwise some mercurial stuff does not > work (complains of not having _ssl, I think). The sort of thing which > does not work is pull/push requests froma remote repository. > > This is a real nuisance, and I have long wanted a way to get this > built when I first build Sage, and not as an afterthought. If the > current discussion will help that, I would be grateful! (Also if > anyone can say what magic would make this work with Sage as currently > organised.)
Well, I wouldn't mind having openssl a /standard/ spkg, which only gets installed if SSL is missing or the present library isn't functional (we should test that first), although it is currently 3.1 MB (openssl-1.0.0.p0.spkg), which isn't /that/ small. But perhaps we could drop the GNUTLS spkg. In the long run, I think we should change our prerequisites script and make a couple of currently-standard spkgs optional, and/or offer different tarballs (e.g. with and without GCC, or Fortran). I know we don't want [to require] internet connections *during* the build, but to me it doesn't make much of a difference whether the prerequisite script tells (e.g. Linux users) "use your package manager to install package foo, bar and baz first", or says "Please install the optional packages x and y first, or choose another tarball.", or queries the user whether he wants to automatically download these now. Perhaps we should also provide some prerequisites checking script *separately*, such that users could check *in advance* what they'd have to download/install or /which/ Sage tarball they should choose to download. Since #10492 [1] now *generates* the Makefile (previously spkg/ standard/deps) anyway, we could easily add dependencies (i.e., include usually "optional" spkgs like openssl, but also iconv etc.) on-the- fly. -leif [1] http://trac.sagemath.org/sage_trac/ticket/10492 -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
