On Fri, Nov 9, 2018 at 2:14 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > On Fri, Nov 9, 2018 at 8:01 AM Erik Bray <erik.m.b...@gmail.com> wrote: > > > > On Fri, Nov 9, 2018 at 1:50 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > > > > > On Fri, Nov 9, 2018 at 7:40 AM Erik Bray <erik.m.b...@gmail.com> wrote: > > > > > > > > Can someone remind me again why SSL libs aren't provided by the system > > > > on macOS, and/or why those libs can't be used for building Python's > > > > ssl module? > > > > > > > > > > Apple switched to their own SSL implementation. > > > They were shipping OpenSSL's headers in some obscure places, shifting > > > from one release to another, > > > in their Xcode, for porting purposes. Not sure whether they are still > > > there nowadays. > > > That's why on OSX one has to build OpenSSL from source. > > > > MFW Microsoft supports open source development better than Apple these > > days.... >_< > > > > In that case, I give up any opposition I might have about adding an > > OpenSSL Sage spkg. I personally do not care in the slightest about > > the licensing issues but I'll let the rest of you care about that. > > > > With the work from https://trac.sagemath.org/ticket/24919 which you > > (Dima) have helped so much to advance, we should be able to disabling > > building OpenSSL if a working installation can be detected on the > > system :) > > for the continuation of #24919, where more Sage's packages are flipped > to the system ones > if possible, see https://trac.sagemath.org/ticket/26286
For any *new* package that ought to just be part of adding the package--implementing the spkg-configure.m4 that is. There is still a lack of documentation on that though. I'll open a ticket to remind myself to do that (I'll CC you as well since you'll have some insights from your work on #26286). > > > > Surely the Python community at large has some experience with this but > > > > I don't really know what that experience constitutes... > > > > On Fri, Nov 9, 2018 at 11:02 AM Nicolas M. Thiery > > > > <nicolas.thi...@u-psud.fr> wrote: > > > > > > > > > > > > > > > I once again got bitten yesterday by installations of Sage without SSL > > > > > support. And thus no pip. Which made me check on Openssl's web page > > > > > which now states that "OpenSSL is licensed under an Apache-style > > > > > license". > > > > > > > > > > If this can help Sage having systematic support for SSL (e.g. through > > > > > openssl as standard package), that would be great! > > > > > > > > > > Cheers, > > > > > Nicolas > > > > > > > > > > [1] https://www.openssl.org/ > > > > > > > > > > On Sat, Mar 31, 2018 at 07:01:45AM -0700, Emmanuel Charpentier wrote: > > > > > > Due notice taken. That would simplify [1]Trac#24107 (which is > > > > > > currently > > > > > > dormant, due to the undergoing changes in the configutation > > > > > > system) > > > > > > enormously. > > > > > > -- > > > > > > Emmanuel Charpentier > > > > > > Le samedi 31 mars 2018 14:06:11 UTC+2, Volker Braun a écrit : > > > > > > > > > > > > [2]https://www.openssl.org/blog/blog/2018/03/01/last-license/ > > > > > > They want to change the license in the next release, which is > > > > > > currently > > > > > > in Alpha, and tentatively set for May. > > > > > > On Saturday, March 31, 2018 at 11:44:58 AM UTC+2, Thierry > > > > > > (sage-googlesucks@xxx) wrote: > > > > > > > > > > > > Hi, > > > > > > not sure whether there is a database access issue, but > > > > > > according to > > > > > > [1], > > > > > > there is no contributor to be found for relicensing openssl. > > > > > > That > > > > > > would be > > > > > > awesome. > > > > > > Ciao, > > > > > > Thierry > > > > > > [1] [3]https://license.openssl.org/trying-to-find > > > > > > > > > > > > -- > > > > > > You received this message because you are subscribed to the > > > > > > Google > > > > > > Groups "sage-devel" group. > > > > > > To unsubscribe from this group and stop receiving emails from > > > > > > it, send > > > > > > an email to [4]sage-devel+unsubscr...@googlegroups.com. > > > > > > To post to this group, send email to > > > > > > [5]sage-devel@googlegroups.com. > > > > > > Visit this group at > > > > > > [6]https://groups.google.com/group/sage-devel. > > > > > > For more options, visit [7]https://groups.google.com/d/optout. > > > > > > > > > > > > Références > > > > > > > > > > > > 1. https://trac.sagemath.org/ticket/24107 > > > > > > 2. https://www.openssl.org/blog/blog/2018/03/01/last-license/ > > > > > > 3. https://license.openssl.org/trying-to-find > > > > > > 4. mailto:sage-devel+unsubscr...@googlegroups.com > > > > > > 5. mailto:sage-devel@googlegroups.com > > > > > > 6. https://groups.google.com/group/sage-devel > > > > > > 7. https://groups.google.com/d/optout > > > > > > > > > > Nicolas > > > > > -- > > > > > Nicolas M. Thiéry "Isil" <nthi...@users.sf.net> > > > > > http://Nicolas.Thiery.name/ > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "sage-devel" group. > > > > > To unsubscribe from this group and stop receiving emails from it, > > > > > send an email to sage-devel+unsubscr...@googlegroups.com. > > > > > To post to this group, send email to sage-devel@googlegroups.com. > > > > > Visit this group at https://groups.google.com/group/sage-devel. > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "sage-devel" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to sage-devel+unsubscr...@googlegroups.com. > > > > To post to this group, send email to sage-devel@googlegroups.com. > > > > Visit this group at https://groups.google.com/group/sage-devel. > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "sage-devel" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to sage-devel+unsubscr...@googlegroups.com. > > > To post to this group, send email to sage-devel@googlegroups.com. > > > Visit this group at https://groups.google.com/group/sage-devel. > > > For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sage-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to sage-devel+unsubscr...@googlegroups.com. > > To post to this group, send email to sage-devel@googlegroups.com. > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
