On Wed, Feb 9, 2011 at 10:47 AM, Clint Byrum <[email protected]> wrote: > On Wed, 2011-02-09 at 10:35 +0100, Olaf van der Spek wrote: >> On Wed, Feb 9, 2011 at 7:21 AM, Clint Byrum <[email protected]> wrote: >> > IIRC, libdrizzle was given a BSD license to avoid the ambiguity >> > surrounding libmysqlclient's "client exception" due to mysql's dual >> > license nature. Strategically, making a GPL network service, with LGPL >> > plugin bindings, and a BSD network access library, seems the best way to >> > balance the desire to keep things Free and open source without hindering >> > adoption. >> >> The problem is that libdrizzle contains LGPL (.c files) according to Marc. >> > > This doesn't really create any issues. Distributing and compiling one > with the other is fine. It does mean that the end product is fully > subject to the LGPL. > > This only matters when you want to change the license of something that > *bundles* libdrizzle on windows. Basically you can't hide libdrizzle in > something else, on windows.
It also means libdrizzle itself is LGPL and not BSD (IMO). -- Olaf _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
