On 2/11/12 3:36 PM, Michael Orlitzky wrote:
On 02/11/2012 04:11 PM, Jason Grout wrote:
On 2/11/12 3:05 PM, Michael Orlitzky wrote:
On 02/11/2012 03:48 PM, Keshav Kini wrote:
As long as we provide instructions on how to use nginx as a backend to
provide SSL, we're not really losing functionality, just increasing
inconvenience a bit for those who want to use SSL.
It could even work out of the box. There shouldn't be a problem
distributing apache/nginx linked against OpenSSL in the sage tarball.
The sage tarball is licensed GPLv3(+?), so I think the same problem is
there.
A tarball isn't really licensed, the code is. Is shipping
sage+apache.tar really different than sage.tar and apache.tar when they
contain exactly the same files?
The GPL extends to cover all code shipped together, IIRC. So it is
different, in my understanding.
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
