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.
Have you managed to change anytihing in the sources yet?
Yes, it's not *that* hard, but it's important to remember that when I say "fork" I mainly mean "fix bugs", fixing bugs is a lot easier than developing new features, but personally I don't see the need for any new features.
The main problem with the sources is the utter crazyness that went into naming, but once you are over that the actual code isn't that insane.
> They even didn't publish regression tests, I think we should push
SAP do publish them, otherwise forking will be close to impossible.
Yes a testsuite is a major missing feature, but it's also something that every user can write, so if everyone who uses the DBMS writes a set of tests that test the features they care about and if everyone who thinks they found a bug writes a test program that will detect the bug then we would get most important features covered in realatively short order.
... but you are right it's a major job.
This could be possible.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.
Yes and it would be very easy to do, if done right it could be the fall-back for the real LGPL'ed client lib which might become unusable at times when catching up to changes in the mysql/sapdb kernel.
-- 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
