4 ms·
Once you statically like that MIT licensed code to GPL licensed code, you have a GPL licences executable. If the source is provided, I think you're in complianc
by phkahler 7y ago
Once you statically like that MIT licensed code to GPL licensed code, you have a GPL licences executable. If the source is provided, I think you're in compliance with the GPL. IANAL and that is a very interesting situation.
That type of thing is why I think people need to choose one of: GPL, LGPL, MIT, BSD (isn't that essentially MIT?). I dont see the point in other "open source" licenses, they primarily create compatibility issues.
- ChrisSD 7y agoAccording to Stallman, MIT is compatible with GPL but the reverse isn't true. You can freely use MIT code (including linking) in a GPL project so long as the source is available. In Rust most code is dual licensed as MIT or Apache 2. You can pick which one to use although IIRC Apache 2 is considered the "primary license" because it provides protections from patent trolls and an explicit contribution licensing clause. However Apache 2 isn't compatible with GPL.
- belorn 7y ago> According to Stallman, MIT is compatible with GPL but the reverse isn't true What are you talking about? Let say we have code A licensed as MIT and code B licensed GPL. You can combine A with B and distribute it. You can combine B with A and distribute it. AB or BA is both a legal combination that a distributor can do. In both cases the distributor need to follow the condition of both MIT and GPL. You can not distribute AB and only follow GPL, or combine BA and only follow MIT. There is two ways to look at copyright licenses. The slightly incorrect but slightly easier way is to see them as a contract. In order to distribute you need to follow the conditions. If you have two contracts then you have two sets of conditions. Three contracts and three sets of conditions. The second way, which lawyers prefer as the more "true" perspective, is to see a copyright license as a list of permissions. Copyright law dictate that as a distributor you have no rights, so the license is the specific conditions in order to gain permission. It is like a airplane ticket where in order to travel you got to follow the rules and conditions or the airline. Countries can also have conditions and rules like visas, passports and enter/exiting laws. Thus in order to have permission to travel between countries you need to follow both sets of rules and conditions. Incompatibility occur when the rules and conditions of two or more licenses demand something impossible, like the case where one condition require an action and the other forbid said action. Both conditions can not be met at the same time and thus the licenses are incompatible.
- ChrisSD 7y agoI mean you can very easily add MIT code in a GPL licensed project because MIT is more permissive. However adding GPL code to an MIT licensed project means you now have to comply with GPL's more restrictive "list of permissions" when you weren't before.
- ryukafalz 7y agoSure, but that doesn't mean the two are incompatible! It just means that you also now have to comply with the terms of the GPL if you use GPL-licensed code in that project: something that the MIT license is flexible enough to allow.
- belorn 7y agoIf we imagine a project with only MIT code that want to add GPL licensed code, the only significant additional legal action needed to be compatible is that you now need to give a patent grant that covers the combined work, and in the case of GPLv3 not distribute the combined work in hardware devices that use access control to prevent the installation of modified versions by the owner. If neither aspects is an issue then the additional work needed to add GPL code to an MIT licensed project is practically zero. There are however naturally implication for downstream which in combination of additionally third licenses (such as proprietary licenses) can cause real issues, and the relationship between such downstream and the MIT project could as a result lead to reasons why the MIT project feel like they can not include GPL into their code. There might even be contractional reasons involved which mean not only do you now have three different copyright licenses to follow but you also have contract law involved in order to follow the law and have a legal right to distribute the combined work. I can see how the permissive licenses in those kind of situation feel simpler since they do not interact much with the other legal stake holders.
- PeterisP 7y agoIf a project with only MIT code adds GPL licensed code, then they can't distribute the "merged" new set of code under the MIT license. Previously, someone could use your MIT code in a closed source product and distribute the resulting executables to their customers without including the source. In the future, that someone would have to start following the GPL rules or stop using your not-MIT-anymore project.