On 2009-Nov-04 01:28:45 +0000, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: >William said the other day the way around this is to build the OpenSSL >libraries >first. Then I looked and see that the OpenSSL libraries were at one time >included in Sage, but were removed since they are not GPL. This was done in >ticket #478 > >http://trac.sagemath.org/sage_trac/ticket/478
A read through the LICENSE files found in various spkg files turns up a number of non-GPL packages (and most don't have LICENSE files so the license can't be quickly determined). The most obvious non-GPL spkg is Python, most of the others are BSD-style licenses. The OpenSSL licenses are basically BSD but still include the advertising clause (I haven't found any other spkgs with that). Maybe we need to revisit and clarify the rationale behind the statement in ticket 478. -- Peter Jeremy
pgpd81FPb5TGG.pgp
Description: PGP signature
