#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, #13384  |      Stopgaps:          
----------------------------------+-----------------------------------------

Comment (by jhpalmieri):

 So the "ssl" target should install openssl, then build Sage, then install
 pyopenssl. Fortunately, the openssl spkg has very few requirements: patch
 should be enough, I think (and patch is necessary on Solaris, at least:
 the system's patch is brain-dead).

 So if the ssl makefile target should include openssl, perhaps it should
 run a script to download the spkg and then maybe modify
 spkg/standard/deps, adding openssl in the appropriate place (after patch).
 Or maybe, given the change at #13373, you could add three (?) new targets:

 - "patch", which does `./sage -i patch`
 - "openssl", which has patch as a prerequisite and does `./sage -i
 openssl`
 - "sslbuild", which has openssl as a prerequisite and just builds Sage.

 Then "ssl" would have "sslbuild" as a dependency and would do `./sage -i
 pyopenssl`. This all seems kind of clunky, especially since we should only
 install openssl if necessary.

 Other ideas:
 - force the user to read README.txt and install openssl manually (`./sage
 -i patch; ./sage -i openssl`), and then `make ssl` will take care of
 everything else, by building Sage and installing pyopenssl.
 - include a script to check whether openssl is present, and run it as part
 of `make ssl`. If openssl is not present, exit and tell the user to
 install it.

 (Wouldn't it be nice if Sage used configure? Then the user could do
 `./configure --ssl=True; make` and the script would figure out whether
 openssl was necessary, and also install pyopenssl at the end.)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13385#comment:22>
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.

Reply via email to