Now do we need to GPL the project?
I don't think so, but IANAL.
If yes, could someone point out the relevant passages in the GPL?
The relavant section is #2:
---- These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. ----
So, if you distribute the application and the DBMS as separate works then you can choose a non-GPL license for your application.
However, the GPL faq addresses the question of GPL-ed plugins loaded by non-free applications (something that is roughly similar to using a GPL'ed driver in a non-free application):
http://www.gnu.org/licenses/gpl-faq.html#GPLPluginsInNF
The difference seems to lie in the definition of "plugin", I believe that a plugin is a module that can be used only in that single application and that both works are dependant on each other to work.
The application/driver relationship is different in that both works are useful without the other and that clearly shows that they are separate and independant works.
I think that you can: 1) Distribute a GPL'ed SAP DB (well duh) 2) Distribute your non-free application (well duh) 3) Configure a non-free application to use a GPLed DBMS as long as you do not distribute the resulting system.
However I don't quite know if you are allowed to do #1 and #2 and then (show up at / ssh to) the customers location and do #3, does anyone know?
-- 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
