3 ms·

Thanks - this helps. I had read the FAQ but wasn't certain what to think after reading the plugin question. The library I have in mind definitely doesn't call

by sp 18y ago

Thanks - this helps. I had read the FAQ but wasn't certain what to think after reading the plugin question. The library I have in mind definitely doesn't call back into the main app (as the faq answer says) and they share data structures only in the sense of the library taking parameters.. not sharing in the shared memory sense of both accessing an in-memory structure being maintained by the program. Quite a gray area.. but it does seem clear as to the intent now. Thanks for the sanity check!

cperciva 18y ago
One way of looking at it is this: Does the plugin make sense without the context of the program which calls it? This viewpoint has been used by some hardware companies with respect to their linux drivers -- they start by writing a FreeBSD driver, and then port that driver to linux. The FreeBSD driver (which contains all the details which they want to keep secret) is obviously not a "derived work" of linux, so this keeps them safe from any arguments about GPL taint.