More reasons to dislike the GPL
In an interview
with Stallman, the following question came up:
If I take a patch under GPL 3 and merge it with a project under
"GPL 2 or later," should I write that the new license for the whole project is GPL 3? The
merged program as a whole
can only be used under GPL 3. However, the files you did not change could still
carry the license of "GPL 2 or later." You could change them or
not, as you wish. |
This means that beyond managing the complexity of a project, with enough
versioning problems between the components that I’m creating and the
components that I’m using. Now I need to worry about the version of the
GPL that the patches are under?
Comments
Comment preview