Geek Answers Handbook

Program with plugins: GPL with LGPL?

I have two different projects:

  • The program that I want to release under the GPL.
  • Plugin API: plugins are written using the interfaces in this API, and the program uses the API to interact with the plugins. I want to release the Plugin API with the LGPL license.

One problem is that I do not want plugins to have to reveal their source. Will they be “infected” by the GPL? They will be compiled against the API and do not need a source to compile the program.

Another problem is that all this talk about “static binding” for LGPL: the program and API are written in Java. Does it matter?

In any case, my main question is: is there any point in releasing a program with the GPL and its public API with LGPL?

+4
source share
2 answers

If you are writing your application from scratch, you can license it as you wish. If you want to make an exception for the GPL for plugins, there is a precedent. A GPL Linking Exception (like Classpath exception) is what you are looking for.

+5
source

This is your copyright. It’s easy to add text to say, “I don’t interpret the plugin API as causing the GPL infection of the plugins.”

IANAL.

0
source

More articles:


All Articles