转售经GPL,MIT许可的开放源代码 [英] Reselling Open Source Code licenced under GPL, MIT

查看:154
本文介绍了转售经GPL,MIT许可的开放源代码的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想使用一些开放源代码,这些开放源代码已获得以下"GNU通用公共许可证(GPL),MIT许可证"的许可.我想将此代码包含在我将要销售的产品中.

I want to use some open source code that is licenced under the following "GNU General Public License (GPL), MIT License". I want to include this code in a product that i will sell.

此处的代码特别

我该怎么办才能不被起诉? :)

What do i have to do to not get sued? :)

我不介意分发修改后的源代码,但我不希望整个应用程序都开源.

I dont mind distributing the source code that i have modified, but i dont want the whole application open source.

如果我将开放源代码构建到一个库中并开放源代码,那么我可以链接到该库而不打开其他源代码吗?

If i build the open source code into a library and open source the library can i link to it and not open the rest of my source?

在项目中,它具有以下

"mda VST插件是根据MIT许可或GPL发行的 或者是许可证的第2版,或者是(根据您的选择)任何更高的版本."

"The mda VST plug-ins are released under the MIT license or under the GPL "either version 2 of the License, or (at your option) any later version"."

推荐答案

您将必须专门查看代码的各个部分,以了解每个许可的方式.尽管GPL和MIT许可证是不兼容的",但这并不意味着不能同时使用这两个许可证来授予代码许可. GPL许可证很可能在那里,以便使用GPL的人可以将其包括在他们的项目中,而MIT许可证则是让其他未使用GPL的人在那里的项目中使用它.

You will have to look specifically at the individual bits of code to know how each is licensed. While the GPL and MIT license are "incompatible" that does not mean that the code can not be licensed using both licenses. The GPL license may well be there so that folks using the GPL can include it in their projects, while the MIT license is there to let others, not using the GPL, use it in there projects.

如果是这种情况,则该代码是双重许可的,那么您只需选择将MIT许可证用于希望包含在项目中的代码即可,而不是GPL许可证.

If that is the case, that the code is dual licensed, then you would simply choose to use the MIT license for the code you wish to include in your project, instead of the GPL license.

如果提到这两个许可证是因为有些是GPL,有些是MIT"(在Sourceforge页面上查看10秒钟并不清楚),那么您将必须知道哪个许可证适用于哪个模块.

If the two licenses are mentioned because "some are GPL and some are MIT" (this was not clear with a 10 second look at the Sourceforge page), then you would have to know which applies to which module.

无论哪种方式,给作者的简单注释都应轻松阐明您明确希望使用的代码的状态.

Either way, a simple note to the author should easily clarify the status of the code you specifically wish to use.

这篇关于转售经GPL,MIT许可的开放源代码的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆