Le 09/01/2012 17:39, William Stein a écrit :
Hi Sage-Devel,
PROPOSAL: I propose that we remove python_gnutls, gnutls, opencdk,
libgcrypt, and
libgpg_error from Sage-5.0. See below for details.
Removing the above 5 packages will save space, make Sage build more
quickly and easily, and make the release manager and developer's job
easier. The only loss in functionality is that some people might not
have support for "secure=True" *out of the box*. For individual users,
I think using ssh tunnels is much better than https anyways. For
localhost users, secure=True is irrelevant. For people setting up a
server who will user secure=True, they *should* get a properly signed
certificate, so they are likely very sophisticated users willing to do
some extra work (incidentally, I have never once in the history of
Sage heard of anybody successfully run a Sage notebook server using
secure=True with a valid non-self-signed certificate!).
When I originally pushed to have secure=True easily available by
default in Sage for all users, I (1) didn't understand that
secure=False is safe on localhost, (2) didn't understand how easy ssh
port forwarding is, and (3) didn't realize how important (and
socially difficult) it is to have a non-self-signed certificate.
Answer:
[X] Yes, remove them!
... and make as many other things "use what's available on the system if
possible" as possible.
Snark on #sagemath
--
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
