Le dimanche 12 février, Jeroen Demeyer a écrit: > On 2012-02-11 22:21, Julien Puydt wrote: > > Le samedi 11 février, Jeroen Demeyer a écrit: > >> On 2012-02-11 22:05, Michael Orlitzky wrote: > >>> It could even work out of the box. There shouldn't be a problem > >>> distributing apache/nginx linked against OpenSSL in the sage > >>> tarball. > >> Why not directly link to OpenSSL then? If you require people to > >> have OpenSSL for apache/nginx, you might as well skip the extra > >> step of apache/nginx. > > > > This isn't the same situation at all! > > I think it pretty much *is* the same situation license-wise. You are > just replacing the non-GPL openSSL by the non-GPL apache. But I am > not a lawyer, so I won't bother discussing this further.
I'm not a lawyer either, but as far as I know it isn't a problem to connect a browser under any licence to a server under any licence... Snark on #sagemath -- 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
