I'm building a project that uses source from a project that's been built from a project that uses code under MIT and GNU licences.
我正在构建一个项目,该项目使用来自项目的源代码,该项目是在使用MIT和GNU许可证下的代码的项目中构建的。
What steps do I need to take to make sure that the source has the correct licence files in the right places?
我需要采取哪些步骤来确保源在正确的位置具有正确的许可证文件?
The project in question is a php plugin for another app, not an executable.
有问题的项目是另一个应用程序的php插件,而不是可执行文件。
1 个解决方案
#1
If you mix code it must comply with both licenses, which generally means they must be compatible. I believe MIT is pretty easy to merge with GPL as long as you obey the following:
如果混合代码,它必须符合两个许可证,这通常意味着它们必须兼容。我相信MIT很容易与GPL合并,只要你遵守以下规定:
The MIT License
麻省理工学院许可证
Copyright (c)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
特此授予任何获得本软件和相关文档文件(“软件”)副本的人免费许可,无限制地交易本软件,包括但不限于使用,复制,修改,合并的权利根据以下条件,出版,分发,再许可和/或出售本软件的副本,并允许向其提供本软件的人员这样做:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
上述版权声明和本许可声明应包含在本软件的所有副本或实质部分中。
Which seems to imply the only requirement is to place the license file with an "substantial" portions of code. It should NOT override the GPL though because the language of GPL is more strict and requires the MIT portions to become GPL (in your version). In other words your whole software must be GPL.
这似乎意味着唯一的要求是将许可文件与“实质”部分代码放在一起。它不应该覆盖GPL,因为GPL的语言更严格,并且要求MIT部分成为GPL(在您的版本中)。换句话说,您的整个软件必须是GPL。
#1
If you mix code it must comply with both licenses, which generally means they must be compatible. I believe MIT is pretty easy to merge with GPL as long as you obey the following:
如果混合代码,它必须符合两个许可证,这通常意味着它们必须兼容。我相信MIT很容易与GPL合并,只要你遵守以下规定:
The MIT License
麻省理工学院许可证
Copyright (c)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
特此授予任何获得本软件和相关文档文件(“软件”)副本的人免费许可,无限制地交易本软件,包括但不限于使用,复制,修改,合并的权利根据以下条件,出版,分发,再许可和/或出售本软件的副本,并允许向其提供本软件的人员这样做:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
上述版权声明和本许可声明应包含在本软件的所有副本或实质部分中。
Which seems to imply the only requirement is to place the license file with an "substantial" portions of code. It should NOT override the GPL though because the language of GPL is more strict and requires the MIT portions to become GPL (in your version). In other words your whole software must be GPL.
这似乎意味着唯一的要求是将许可文件与“实质”部分代码放在一起。它不应该覆盖GPL,因为GPL的语言更严格,并且要求MIT部分成为GPL(在您的版本中)。换句话说,您的整个软件必须是GPL。