Greetings
It has come to my attention that at least one instance of LGPL violation
has occured with respect to SDL. I imagine that this kind of violations
may also be more common, but I haven’t bothered to spesifically seek
more of them out.
The issue is that some projects based on SDL choose to create binary
distributions that include prebuilt SDL libraries, rather than just
distributing their own binaries and instructing the people downloading
them to get the SDL libraries from the SDL homepages, for example. Now
this in itself of course isn’t a license violation, if they’d distribute
also the appropriate source code for the SDL library. Not all do.
I would, in the interest of keeping (L)GPL licensing matters clear, urge
the SDL developers to contact people found doing this sort of things and
ask them to comply with SDL’s LGPL license. As the source distribution
clause is clearly spelled out on the SDL homepage as well, I assume you
might agree. (The alternative would be to clarify this kind of use as
acceptable as an exception to the LGPL, but that’d make things
complicated and lessen the availability of the source code.)
Anyway, the particular offending page that propmpted this mail is at
URL:http://teddy.sourceforge.net/. The Windows binary package contains
SDL DLL’s, but no sources are available from the pages.
Thank you for your attention.–
Mikko Rauhala - @Mikko_Rauhala - URL:http://www.iki.fi/mjr/
- WTA member - URL:http://www.transhumanism.org/
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20020628/561976a5/attachment.pgp