LGPL/GPL许可 [英] LGPL/GPL licensing

问题描述

我有一个使用LGPL下的组件的商业Web应用程序. 由于此组件具有插件架构， 现在，我为此组件创建了一个使用库(LGPL)的插件. 该库使用的数据源是GPL.

I have a commercial web app that uses a component under LGPL. Since this component has a plug in architecture, I have now created a plug for this component that use a library (LGPL). This library uses a data source which is GPL.

这是否意味着我必须释放Web应用程序的源代码?还是只是需要释放插件的源代码?

Does this mean I have to free the source for my web app? or is it just necessary to release the source for the plug in?

感谢您的投入和建议，请原谅我的英语不好.

Thanks for any input and advice, and forgive me for my poor English.

推荐答案

要100％确定，您应该阅读常见问题解答，然后联系熟悉软件许可的律师.不要与并非如此的律师交谈，因为他们会告诉您不要为了安全起见而不要使用任何免费/开源的软件，任何人都可以说.

To be 100% sure, you should read FAQ and then contact a lawyer who is familiar with software licensing. Don't talk to the lawyers who aren't because they'll tell you not to use anything free/opensource just to be on the safe side, which anyone can say.

无论如何，数据源是GPL"是什么意思? GPL源代码是否已链接到您的应用程序?

Anyway, what do you mean by "data source which is GPL"? Is GPL source code being linked into your application?

常见问题解答(FAQ)中有几个关于插件和GPL的问题.

There are several questions in the FAQ regarding plug-in and GPL.

我可以发布非免费程序吗 旨在加载GPL覆盖的内容 插件?

Can I release a non-free program that's designed to load a GPL-covered plug-in?

这取决于程序如何调用 它的插件.例如，如果 程序仅使用简单的fork和exec 调用并与之通信 插件，那么插件是 单独的程序，因此 该插件没有要求 关于主程序.

It depends on how the program invokes its plug-ins. For instance, if the program uses only simple fork and exec to invoke and communicate with plug-ins, then the plug-ins are separate programs, so the license of the plug-in makes no requirements about the main program.

如果程序 动态链接插件，它们 相互进行函数调用，以及 共享数据结构，我们相信它们 形成一个程序，必须 被视为两者的扩展 主程序和插件.在 为了使用GPL涵盖的插件， 主程序必须被释放 根据GPL或与GPL兼容的免费版本 软件许可，以及该条款 当 分发主程序以供使用 这些插件.

If the program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. In order to use the GPL-covered plug-ins, the main program must be released under the GPL or a GPL-compatible free software license, and that the terms of the GPL must be followed when the main program is distributed for use with these plug-ins.

如果程序 动态链接插件，但是 他们之间的沟通是有限的 调用 带有一些选项和等待的插件 为了它返回，这是一个边界 情况.

If the program dynamically links plug-ins, but the communication between them is limited to invoking the ‘main’ function of the plug-in with some options and waiting for it to return, that is a borderline case.

使用共享内存与复杂的数据结构进行通信几乎等同于动态链接.

Using shared memory to communicate with complex data structures is pretty much equivalent to dynamic linking.

正如其他人指出的那样，未分发的Web应用程序似乎在普通GPL下被视为私人使用(不是在Affero GPL中?).

As others have pointed out, web apps that are not distributed seems to be considered private use under plain GPL (not in Affero GPL?).

某公司正在运行修改后的 网络上的GPL程序版本 地点. GPL是否说他们必须 释放修改后的资源?

A company is running a modified version of a GPL'ed program on a web site. Does the GPL say they must release their modified sources?

GPL允许任何人制作修改后的版本并使用它，而无需将其分发给他人.该公司正在做的事情就是其中的一个特例.因此，该公司不必发布修改后的源.

The GPL permits anyone to make a modified version and use it without ever distributing it to others. What this company is doing is a special case of that. Therefore, the company does not have to release the modified sources.

对于人们来说，至关重要的是，可以自由进行修改并私下使用它们，而不必发布这些修改.但是，将程序放在服务器计算机上以供公众交谈几乎不是私人"使用，因此在这种特殊情况下要求发布源代码是合法的.希望解决此问题的开发人员可能希望将GNU Affero GPL用于设计用于网络服务器的程序.

It is essential for people to have the freedom to make modifications and use them privately, without ever publishing those modifications. However, putting the program on a server machine for the public to talk to is hardly "private" use, so it would be legitimate to require release of the source code in that special case. Developers who wish to address this might want to use the GNU Affero GPL for programs designed for network server use.

这篇关于LGPL/GPL许可的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！