Geek Answers Handbook

Licensed software using GPLs with non-GPL licenses

Let's say I write some code that we will call X. It uses some GPL code, let it call it the Y library. Obviously, I will need to release X with a GPL. It's great. My question is: can I additionally release X under a license such as MIT, so if someone needs X, not Y, they don’t need to use it with the GPL?

+5
source share
5 answers

YES, you can free the source code of any license. You have this right under US copyright law.

However, if you use any GPL source code in your source code (or distribute with any GPL code), you must use the GPL license for all work. This is because you must accept their license to use your code.

BTW. I am not a lawyer.

+3
source

The MIT license is also compatible with the GPL, which means that the GPL allows you to combine and redistribute software that uses the MIT license. This link should provide you with comprehensive analysis. There are many ifs and buts and definitions around libraries vs plugins vs modules, etc. that you should familiarize yourself with.

+1
source

: X , X MIT ( - )?

:

  • , X GPL- Y / X.
  • , X , GPL, Y, .

Y, X MIT - (, Linux -, ) GPL .

, MIT, , .

, , .

, :

  • X GPL, GPL Y . ( " " )
  • X GPL/MIT, GPL Y , , MIT, ( ) X Y. ( )
  • X MIT, GPL- Y , , - Y. ( , ).

, .

+1

, , , , , .

GPL, GPL, GPL. IPython, , readline, / , , GPL, . (, .)

0

, GPL; GPL, . ​​Linux , .

, (/ , ); , . , Dependency HELL!!!

HELL, :

  • DLL Hell
  • DSO Hell
  • Jar Hell
  • RPM Hell

  • define 1 0

, :

A few long chains of multiple circular and conflicting dependencies that feed on your brain drain your soul !!!

-1
source

More articles:


All Articles