Sage-Tips

Can I use LGPL in closed source?

Applying LGPL to a library ensures that the library itself and any modified versions of it will remain open source. But it can be used by closed source software.

Can you use GPL in closed source?

@eMAD parts of it can, yes. For example if it has GPLed JavaScript, then the source code for that must be available.

Can I use GPL in LGPL?

Note that the LGPL is compatible with the GPL: you can decide to “upgrade” to GPL and incorporate it in a wholly GPL licensed project if you wish. You can’t however go the other way and re-license GPL licensed code as LGPL.

Can I use GPL v3 to distribute my software?

You may copy, distribute and modify the software as long as you track changes/dates of in source files and keep modifications under GPL. You can distribute your application using a GPL library commercially, but you must also provide the source code. GPL v3 tries to close some loopholes in GPL v2.

Is it legal to distribute GPL programs on non-GPL OS?

We can force such rules in the jungle, but in real life (juridical of country or state) it depends on who, whom, when and what. The legal problem (law) raise when you do an act of distributing GPL program as binary or library on non GPL OS.

What is the purpose of GPL software?

The abstract purpose of GPL software is for people to have full ownership of their computers. What I mean is that typically, legally speaking, you (the “end user” of the computer) own the hardware of your computer: you can throw it out of a window or install whatever software you want on it.

Can I use GPL code at the DevOps / build layer?

Unless someone in the comments disagrees, I’d like to point out that if you need to use a bit of GPL code at your devops / build layer, you can make that tool a separate application which CAN, potentially, be made open source w/o giving away the product your other-named tool builds. If you use GPL code at runtime, you gotta give out the source.