On 8 April 2015 at 12:26, Thierry <sage-googlesu...@lma.metelu.net> wrote: > Hi, > > this is quite unrelated : pyopenssl is a wrapper to use openssl library > easily via python. Since it is not a standard package, i would suggest to > stop maintaining it (it is bitrotting and upgrading it will require to > maintain 4 additional dependencies) and let the user installing it with > pip if necessary (we did the same with sqlalchemy), see > http://trac.sagemath.org/ticket/17831 > > Here we are dealing with the issue that pip requires that python is built > with openssl, but openssl is not GPL-compatible, hence it can not be part > of the source tarball. So the user either have to install libssl-dev from > her distribution or run `sage -i openssl` before building python.
Thanks for clarifying. I always mix up the pkgs openssl and pyopenssl, so I should have kept quiet. John > > Ciao, > Thierry > > > On Wed, Apr 08, 2015 at 12:01:35PM +0100, John Cremona wrote: >> On 8 April 2015 at 11:53, Vincent Delecroix <20100.delecr...@gmail.com> >> wrote: >> > On 08/04/2015, Daniel Krenn <kr...@aon.at> wrote: >> >> Am 2015-04-08 um 12:28 schrieb Vincent Delecroix: >> >>> At least, does 'sage -i openssl' before 'make' work? >> >> >> >> Seems to be possible (tried; but still compiling). >> > >> > If it does, it would be good to add it to the README and the relevant >> > section in the documentation. >> > >> >> Item 10 in the README says this already: >> >> 10. OPTIONAL: Read this if you are intending to run a Sage notebook >> server for multiple users. For security (i.e., to run >> "notebook(secure=True)") you want to access the server using the >> HTTPS protocol. First, install OpenSSL and the OpenSSL development >> headers on your system if they are not already installed. Then >> install pyOpenSSL by building Sage and then typing >> >> ./sage -i pyopenssl >> >> Note that this command requires internet access. Alternatively, >> "make ssl" builds Sage and installs pyOpenSSL. >> >> John >> >> > Vincent >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "sage-release" group. >> > To unsubscribe from this group and stop receiving emails from it, send an >> > email to sage-release+unsubscr...@googlegroups.com. >> > To post to this group, send email to sage-release@googlegroups.com. >> > Visit this group at http://groups.google.com/group/sage-release. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-release" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-release+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-release@googlegroups.com. >> Visit this group at http://groups.google.com/group/sage-release. >> For more options, visit https://groups.google.com/d/optout. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
