Quote:
Then everyone and your FSF guy (boo, he should know better!) are quite wrong...
Ok, I think we all got here, and this needs some explanation. Here is the text pasted:
Quote:
It depends on how the program invokes its plug-ins. If the program uses fork and exec to invoke plug-ins, then the plug-ins are separate programs, so the license of the plug-in makes no requirements about the main program.
If the program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. In order to use the GPL-covered plug-ins, the main program must be released under the GPL or a GPL-compatible free software license, and that the terms of the GPL must be followed when the main program is distributed for use with these plug-ins.
If the program dynamically links plug-ins, but the communication between them is limited to invoking the `main' function of the plug-in with some options and waiting for it to return, that is a borderline case.
As the first sentence sais: It depends on how the program invokes plugins, and as far as this... "license" only seems to contemplate linux as programming platform, it should be checked if other programming models are fittable.
The old-well-known "use-a-port" technique, might be useful here, as well as some pattern techniques.
The GPL license sais it must share data structures to be ilegal.
I think, we should check this, because as I see it, it doesn't fit well to the vage statements (and we should check too if those statements are legal) the GPL proposes...