views:

135

answers:

1

I'm thinking of building a piece of software on top of another piece of software which is licensed under the GPL. I am planning on licensing and selling the software.

Could anyone who is familiar with the details of the license see any problems or pitfalls of having a dependency on a piece of software licensed under the GPL?

+1  A: 

If you mean GPL, then you have to release the full source code of your product and tools needed to build it. If it is GPL3 and you also sell hardware you have to make sure customers can replace the software on it.

If it is LGPL then you may link to it without the impact above, but not statically!

Subjective: Personnally I think GPL is far too restrictive, I would look for alternative projects under MPL or BSD-like licensing models you could build your software upon.

jdehaan
What about if the product was a plugin, would it have to follow the same conditions?
ChrisInCambo
GPL is often also called a virus-like license. It "contaminates" everything that uses it. So, yes, even if it is a plug-in, you have to release the full source code of the whole product. (I am about 99.9% sure). Maybe a lawyer can confirm for 100%.
jdehaan
The general rule of thumb is if your software links to a GPL library you must make your code GPL. If you can make a plugin without linking to the API(seems impossible?) you might have a shot, but again ask a lawyer to be sure.
Esben Skov Pedersen