问题描述
MIT许可证是GPL兼容的. GPL许可证是否与MIT兼容?即我可以在GPL许可的产品中包含MIT许可的代码，但是我可以在MIT许可的产品中包括GPL许可的代码吗?
The MIT license is GPL-compatible. Is the GPL license MIT-compatible? i.e. I can include MIT-licensed code in a GPL-licensed product, but can I include GPL-licensed code in a MIT-licensed product?
在我看来，MIT许可证与GPL之间的主要区别在于MIT不需要开源，而GPL则需要开源.那是对的吗? GPL是否比MIT许可证更具限制性?
It seems to me that the chief difference between the MIT license and GPL is that the MIT doesn't require modifications be open sourced whereas the GPL does. Is that correct? Is the GPL is more restrictive than the MIT license?
推荐答案
是的-一般.如果您使用的是GPL，则没有拥有开源更改的内容.您可以修改它并将其用于您自己的目的，只要您不分发它即可.但是...如果您确实分发了它，那么使用GPL代码的整个项目也会自动变为GPL.这意味着，它必须是开源的，并且接收者获得与您相同的所有权利-这意味着，他们可以周转并分发，修改，出售它，等等.这将包括您的专有代码，而该专有代码不会不再是专有的-它成为开源.
True - in general. You don't have to open-source your changes if you're using GPL. You could modify it and use it for your own purpose as long as you're not distributing it. BUT... if you DO distribute it, then your entire project that is using the GPL code also becomes GPL automatically. Which means, it must be open-sourced, and the recipient gets all the same rights as you - meaning, they can turn around and distribute it, modify it, sell it, etc. And that would include your proprietary code which would then no longer be proprietary - it becomes open source.
与MIT的区别在于，即使您实际分发使用MIT许可代码的专有代码，也不必使代码开源.您可以将其作为封闭的应用程序分发，该应用程序中的代码已加密或为二进制.只要带有MIT许可通知，包括MIT许可的代码就可以加密.
The difference with MIT is that even if you actually distribute your proprietary code that is using the MIT licensed code, you do not have to make the code open source. You can distribute it as a closed app where the code is encrypted or is a binary. Including the MIT-licensed code can be encrypted, as long as it carries the MIT license notice.
是的，非常如此.
这篇关于MIT与GPL许可证的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！