#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:          
----------------------------------+-----------------------------------------

Old description:

> See [http://thread.gmane.org/gmane.comp.mathematics.sage.devel/54802/
> this sage-devel post by William].
>
> == Task ==
>
> Remove the following SPKGs:
>
>  * python_gnutls
>  * gnutls
>  * opencdk
>  * libgcrypt
>  * libgpg_error
>
> Also:
>
>  * no longer ship pyOpenSSL with sagenb (this will be taken care of in
> #13121)
>  * no longer require OpenSSL dev headers in prereq
>
> == Rationale ==
>
> Read the above linked thread, but basically, `notebook(secure=True)` is
> rarely used, and is not even really that desirable to use, except for
> people setting up multiuser Sage servers, which is a small percentage of
> Sage users. Therefore we will require users who want to use
> `notebook(secure=True)` to perform the additional step of installing
> pyOpenSSL into Sage's Python. This allows us to get rid of our sort of
> problematic dependencies on OpenSSL.
>
> Furthermore, as I understand it, our switching to OpenSSL had already
> made GNUTLS useless in Sage when we started shipping the Flask notebook
> (Sage 5.2), so we can get rid of GNUTLS and related SPKGs at the same
> time.
>
> ----
>
> Apply:
>
> - [attachment:trac_13385-root.patch] and [attachment:trac_13385-root-
> doc.patch] to the root repo
> - [attachment:trac_13385-sage-library.patch] to the Sage library
>
> Copy http://sage.math.washington.edu/home/palmieri/SPKG/prereq-1.1.tar.gz
> to spkg/base.
>
> Still to come: new sagenb spkg (at #13121).

New description:

 See [http://thread.gmane.org/gmane.comp.mathematics.sage.devel/54802/ this
 sage-devel post by William].

 == Task ==

 Remove the following SPKGs:

  * python_gnutls
  * gnutls
  * opencdk
  * libgcrypt
  * libgpg_error

 Also:

  * no longer ship pyOpenSSL with sagenb (this will be taken care of in
 #13121)
  * no longer require OpenSSL dev headers in prereq

 == Rationale ==

 Read the above linked thread, but basically, `notebook(secure=True)` is
 rarely used, and is not even really that desirable to use, except for
 people setting up multiuser Sage servers, which is a small percentage of
 Sage users. Therefore we will require users who want to use
 `notebook(secure=True)` to perform the additional step of installing
 pyOpenSSL into Sage's Python. This allows us to get rid of our sort of
 problematic dependencies on OpenSSL.

 Furthermore, as I understand it, our switching to OpenSSL had already made
 GNUTLS useless in Sage when we started shipping the Flask notebook (Sage
 5.2), so we can get rid of GNUTLS and related SPKGs at the same time.

 ----

 Apply:

 - [attachment:trac_13385-root.patch] and [attachment:trac_13385-root-
 doc.v2.patch] to the root repo
 - [attachment:trac_13385-sage-library.patch] to the Sage library

 Copy http://sage.math.washington.edu/home/palmieri/SPKG/prereq-1.1.tar.gz
 to spkg/base.

 Still to come: new sagenb spkg (at #13121).

--

Comment (by jhpalmieri):

 Here's some documentation for README.txt (the "v2" patch). If it's okay,
 we can add something similar to the installation guide.

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