You can either rely on the non-rebranded versions of
SAP DB or buy a commercial license from MySQL if you do not want that your applications have to be placed under GPL."
This makes me say good bye to my future plans of using Sap-DB in future developments.
Well, there shouldn't be any problems with using only the LGPL client libs, these libs don't change that much, so it's not that hard to maintain a separate fork of the client libs.
I will be maintaining a LGPLed version of the client liberaries until the main mysql/sapdb distribution becomes sensibly licensed, even if that turns out to never happen.
If the mysql people tries to change the license of the kernel itself to GPL+crap then I'm all for maintaining a separate fork of the kernel as well.
There are other ways of sidestepping this entire licensing thing, simply write a GPL'ed proxy that allows the non-GPL applications to talk to it over shared memory and sockets it will add a little latency but compared to everything else it wouldn't be that bad.
-- Regards Flemming Frandsen - http://dion.swamp.dk PartyTicket.Net co founder & Yet Another Perl Hacker
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
