#13385: Remove TLS/SSL-related packages
-------------------------------+--------------------------------------------
Reporter: kini | Owner: tbd
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.3
Component: packages | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: #13121 | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by kini):
Personally I don't think it's worth adding another environment variable to
the long list we already have, just to avoid a small percentage of users
having to run `sage -i openssl` and `sage -i pyopenssl` after `make`.
Furthermore this will set a new precedent. Currently we have no
environment variables which control whether a certain package is installed
or not, except `SAGE_INSTALL_GCC` which is kind of a special case because
we use GCC in Sage regardless of whether it's installed via SPKG or used
from the system. Also, no environment variable causes the Sage build
process to need network connectivity, as this suggestion would (unless you
also want to make pyOpenSSL a standard shipped package).
IMHO installing an SPKG is not a big deal, it's one line and the average
user doesn't need to know about it because they are not running a multi-
user notebook server.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13385#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
