- Thread starter
- #2
Seeing as no one replied to this, I'll update this post with what I found out just in case anyone else has the same question.
So, LGPL means you can link to it via a linker, but if you modify that library's code, you have to publish your modifications or donate them back.
GPL means you must distribute your code even if all you do is link to the library. However, if you never link it in and only run it as an external program via an HTTP interface or some kind of networking, then you only have to distribute your changes to that GPL project, not your own code.
That's why Amazon and all those companies can take a GPL project and sell it in the cloud. That's where the AGPL comes in, and that says, even if you talk to it over the network, you have to release your code. IIRC, it even says it can only talk to other AGPL projects, and anything not AGPL must be released.
So, LGPL means you can link to it via a linker, but if you modify that library's code, you have to publish your modifications or donate them back.
GPL means you must distribute your code even if all you do is link to the library. However, if you never link it in and only run it as an external program via an HTTP interface or some kind of networking, then you only have to distribute your changes to that GPL project, not your own code.
That's why Amazon and all those companies can take a GPL project and sell it in the cloud. That's where the AGPL comes in, and that says, even if you talk to it over the network, you have to release your code. IIRC, it even says it can only talk to other AGPL projects, and anything not AGPL must be released.