Is LGPL applicable for applications?

I am working on an application that will support plugins. I am wondering if I can apply LGPL to an application or LGPL only for libraries?

The main thing is that I want the application to be roughly the GPL, but this does not apply to plugins or scripts downloaded by the application. However, the GPL believes plug-ins should be derived, so a pure GPL is not very good in this case.

I was currently thinking about the MPL, but it clearly states that the license will be under the jurisdiction of California, which is not very acceptable for Europeans.

What would be a more reasonable choice for an application license if I want a weak copy to remain. Are there any standard GPL exceptions that I should apply in place of LGPL, and how does LGPL apply to applications? The license talks about libraries that are pretty confusing for me if I want to apply them to the application.

+5
source share
5 answers

Yes, it can be applied to applications. LGPL3 is a GPL + exception, so it should be appropriate for your application. OpenOffice is an example of a large application that is LGPL, and I find that their reasoning was similar to yours.

+5
source

LGPL , . , , , .

, ( , , ), - Microsoft Reciprocal License ( Microsoft , ):

. , , ( ), , , , , , .

, MPL, , :

"", "", " " "" , .

.

+1

- - , , " ".

, IMHO - , LGPL .

0

, LGPL . LGPL , . , , JBoss, LGPL.

GPL (, GCC). LGPL 3 GPL 3, .

MPL, 2012 , : MPL 2.0: : http://www.mozilla.org/MPL/2.0/. , A/L/GPL 2 3 .

0

GPL .

GPL, linux, , -.

-1

All Articles