Permissive vs Copyleft License Compatibility
What you'll learn: How permissive licenses (MIT, Apache) interact with copyleft licenses (GPL, LGPL) in combined works.
The Core Compatibility Challenge
When you combine code from different sources, their licenses must be compatible—meaning you can legally satisfy all their requirements simultaneously. The friction typically occurs when mixing permissive and copyleft licenses.
Permissive licenses (MIT, BSD, Apache) allow you to use the code in almost any context, including proprietary software. They're like saying: "Use this however you want, just credit me."
Copyleft licenses (GPL, LGPL) require that any combined or derivative work be distributed under the same copyleft terms. They're like saying: "Use this freely, but you must share your modifications under the same terms."
The Compatibility Rules
Permissive → Copyleft: ✅ Works
You can take MIT-licensed code and incorporate it into a GPL project. The MIT license's minimal requirements (attribution) don't conflict with GPL's requirements. The final combined work becomes GPL-licensed, which is more restrictive but legally valid.
Copyleft → Permissive: ❌ Doesn't Work
You cannot take GPL code and put it into an MIT-licensed project. The GPL requires the entire work to be GPL-licensed, which contradicts MIT's permissiveness. You'd violate the GPL by trying to release the combined work under MIT.
Analogy: Think of copyleft as a "viral" license—it spreads to the whole work. Permissive licenses are "immune" when standalone but get "infected" when combined with copyleft code.
The LGPL Exception
The LGPL (Lesser GPL) allows linking with non-GPL code while keeping components separate, creating a middle ground for libraries.
Key Takeaway: Permissive licenses can flow into copyleft projects, but copyleft cannot flow into permissive projects—copyleft always "wins" and governs the combined work.