----- Original Message ----- From: "Flemming Frandsen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 27, 2003 8:16 PM Subject: Re: About the new licensing schema starting with MySQL
> > 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. It is defenitely the only way to protect people who are using SAP/DB in production. Count me in, I would like to help this project. > > 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. > The question that arises is will SAP AG allow us to use SAP/DB name? The likely answer is no. So we will have to come up with a meaningless name, the way Firebird people did. And even with SAP's name on it this database was underrated for its merits. I am willing to help but I've looked at source code. I don't think we will be able to find enough people to work on it. > > 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 Best regards, Nicolai _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
