Including GPL external library in MIT code [closed]

Question

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 6 years ago.

Improve this question

I am shipping software licensed under the MIT license.

Under the application tree, I have also a file that is part of the software. Inside of this file there are the exact contents of an external library, licensed under GPL. There is also other code (by me), licensed under the MIT license. The section of this file that contains the library is left intact and the library is not altered.

Can I release my software under the MIT license? Should I include the GPL license (I'm quite sure the answer is yes)? Should I also include a README with indications such as "the part of the file X is licensed under the GPL license as it is an external library, the rest is MIT"?

Answer 1

Can I release my software under the MIT license?

If you use GPL'ed software in your software (bring together two works) and you then distribute the new work, you have to distribute it under GPL (copyleft).

There are different flavors of GPL which has a different effect on how the copyleft works (GPL, LGPL, AGPL), so if you need more info, you need to be more specific.

Should I include the GPL license (I'm quite sure the answer is yes)?

Yes. Any of the GPL licenses requires this.

Should I also include a README with indications such as "the part of the file X is licensed under the GPL license as it is an external library, the rest is MIT"?

Yes, that is useful. However, if it is really GPL, keep in mind that next to what you write is correct, the whole package has to be distributed under GPL.

See as well

• Maintaining Permissive-Licensed Files in a GPL-Licensed Project: Guidelines for Developers

Answer 2

If you own the code, if the property of the code belongs to you, you are free to change the license everytime and each time you want to, you can also release the same code under more than 1 license.

When redistributing the code obtained from a third part that is released under a GPL license, the only thing that you have to do is to left the terms of the license unchanged because the GPL is intended this way. the GPL stays GPL no matter how many developers or subjects are involved in the "distribution chain".