2009/1/23 Alon Bar-Lev <alon.bar...@gmail.com>: > On 1/23/09, Andreas Jellinghaus <a...@dungeon.inka.de> wrote: >> > It cannot be unless we explicitly specify some exceptions in OpenSC >> > license. A plugin for LGPL should be also GPLed. >> > Read [1] and on. >> >> >> opensc is not under GPL. > > GPL and LGPL are the same, except of that none GPLed application can > be linked with LGPLed application.
Replace "application" by "code". > But.... LGPL application/library cannot have none GPLed dependencies. A LGPL code can only depend on GPL code? Not even LGPL code? So OpenSC (LGPL) can not use the GNU libc since glibc is LGPL and not GPL? > This is to allow GPLed application use LGPLed application without > breaking GPL chain. > So the rules of having a plugin to GPL or LGPL should be the same. As you write bellow the rules do not apply to plugins as long as the plugin respect the publicly available interface. > PKCS#11 or any standard interface which is not depended on a specific > implementation, is an edge condition I discussed with FSF and they > agreed that as long the application and the provider have not implicit > or explicit knowledge about each other it is OK. I agree with the FSF. > You cannot say this on openct plugin as it is openct specific. Why is OpenCT plugin API different from "PKCS#11 API or any standard interface"? Note: you can do whatever you want with a GPL code (mix with proprietary code, etc.) as long as you do not _distribute_ it (but keep it for yourself). Regards, -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
