PS: The openssl master branch is already Apache
licensed:
https://github.com/openssl/openssl/commit/151333164ece49fdba3fe5c4bbdccd9ae66d.
Though no release yet.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
On Friday, March 15, 2019 at 5:12:59 PM UTC+1, Dima Pasechnik wrote:
>
> 1) As Python.org now ships 2.7.16 with pre-build openssl, then why
> don't we do the same?
>
Because Python is not GPL licensed, of course
> (IMHO Sage should not try to out-saint the pope, and stick to "we
> don't ship
On Fri, Mar 15, 2019 at 3:55 PM E. Madison Bray wrote:
>
> On Fri, Mar 15, 2019 at 4:47 PM Dima Pasechnik wrote:
> >
> > On Fri, Mar 15, 2019 at 3:35 PM E. Madison Bray
> > wrote:
> > >
> > > On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
> > > >
> > > > It appears that Sage's openssl p
On Fri, Mar 15, 2019 at 4:47 PM Dima Pasechnik wrote:
>
> On Fri, Mar 15, 2019 at 3:35 PM E. Madison Bray wrote:
> >
> > On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
> > >
> > > It appears that Sage's openssl package is broken on MacOS nowadays.
> > > Should this be a blocker?
> >
> > H
On Fri, Mar 15, 2019 at 3:35 PM E. Madison Bray wrote:
>
> On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
> >
> > It appears that Sage's openssl package is broken on MacOS nowadays.
> > Should this be a blocker?
>
> How is SSL support currently handled in MacOS? I have not kept up
> with
On Fri, Mar 15, 2019 at 3:31 PM Dima Pasechnik wrote:
>
> It appears that Sage's openssl package is broken on MacOS nowadays.
> Should this be a blocker?
How is SSL support currently handled in MacOS? I have not kept up
with that issue. Are OSX users still not able to do something as
simple as
Is openssl compiled into the macos binary? Technically we wouldn't be
allowed to distribute that
On Friday, March 15, 2019 at 3:58:17 PM UTC+1, Dima Pasechnik wrote:
>
> On Fri, Mar 15, 2019 at 2:53 PM Volker Braun > wrote:
> >
> > We don't build it by default, so imho the answer is no. N
On Fri, Mar 15, 2019 at 2:53 PM Volker Braun wrote:
>
> We don't build it by default, so imho the answer is no. Not every optional
> package works on every supported platform, even if we strive for that.
Are we going to ship broken MacOS binaries then?
>
> On Friday, March 15, 2019 at 3:31:36
We don't build it by default, so imho the answer is no. Not every optional
package works on every supported platform, even if we strive for that.
On Friday, March 15, 2019 at 3:31:36 PM UTC+1, Dima Pasechnik wrote:
>
> It appears that Sage's openssl package is broken on MacOS nowadays.
> Should
It appears that Sage's openssl package is broken on MacOS nowadays.
Should this be a blocker?
On Thu, Mar 14, 2019 at 4:49 PM Volker Braun wrote:
>
> Feel free to fix the Cygwin-related bugs, but some of these are longstanding
> issues that should be discussed with upstream first; Realistically
Feel free to fix the Cygwin-related bugs, but some of these are
longstanding issues that should be discussed with upstream first;
Realistically thats not going to make it to the next Sage version.
On Thursday, March 14, 2019 at 2:36:29 PM UTC+1, E. Madison Bray wrote:
>
> Hi Volker,
>
> I don
Hi Volker,
I don't think there should be a release candidate at least until most
of the blocker issues [1] are resolved; in particular the four that
are already either positively reviewed or are in-progress.
Thanks
[1]
https://trac.sagemath.org/query?priority=blocker&status=needs_info&status=n
Next develop release will be rc0
IMHO changes to gmpy2 should wait until the next version to give it some
time to test out.
--
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
13 matches
Mail list logo
