Should I use LGPL or GPL
I'm busy writing an application and I'm not sure if I should use LGPL or GPL (or maybe something else). Here are my restrictions:
Which license would be the best? Also for some of the libraries I change a bit of their source code to fit my application. These are not any major changes to the code itself, but changes to include statements, file extensions, etc, eg:
From (original library):
#include "libx/libx.hpp"
To (my changes):
#include "external/libx.h"
Note the different location and extension. Is this allowed?
You must use GPL if you are using libraries that are GPL.
I can't find it now, but it was on GNU page.
per FSF if you are linking against external GPLd libraried, you must be GPLd yourself.
edit (comment): with that said, one could make an argument if you are only dynamically linking against said GPLd libraries, and not providing them, one doesn't need to. However, This isn't the FSF's position, but no one I know of has ever legally challenged their interpretation.
http://en.wikipedia.org/wiki/GNU_General_Public_License#Libraries has some of the discussion.
Item (1) above locks you into GPL. If you use LGPL you are allowing others to link up with your code in ways where they can write commercial software or just non-GPL software. So, basically, if you want absolutely everything written based on your code to also subsequently be open source, then you must use GPL.
链接地址: http://www.djcxy.com/p/79738.html上一篇: 无法将Hosted应用程序从Tomcat部署到Firefox OS市场
下一篇: 我应该使用LGPL还是GPL