Edson Carlos Ericksson Richter escribi�:
The GPL license is clear: you must distribute sources. Other thing: you can commercialize GPLed software since:
1) You don't sell code: you can get money by the distribution service; 2) You make widely adivisable that the code is copyright by "Name of developer A, Name of developer B", and so on...
So anyone could package and sell SapDB, since the sources be bundled, and the Sap rights are protected.
The real problem is libraries licensing, that don't make able to commercial software to link, dinamycly or not, to GPL software.
Actually, the libraries are LGPL just because this. But if Sap changes the library licenses, I think that even they cannot "plug" their commercial apps to their own SapDB libs (anyone that know laws can explain if is possible a company violate their own license model???)...
Just My2c,
Edson Richter
----- Original Message ----- From: "Fra" <[EMAIL PROTECTED]>
To: "SapDB" <[EMAIL PROTECTED]>
Sent: Thursday, June 12, 2003 11:25 AM
Subject: Licensing...
I have a question about licensing on SAP... If RedHat makes commercial distributions (RedHat Advanced Server) and doesn't give away *all* the sources and limites the redistribution (as their EULA says)... and contains GPL packages (even the kernel)... why couldn't one do the same thing with SapDB?
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.488 / Virus Database: 287 - Release Date: 5/6/2003
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
