The CDDL doesn't have any problems being linked into GPL'ed code, it is the GPL that has a problem accepting CDDL code.
The CDDL doesn't have any problems being linked into GPL'ed code, it is the GPL that has a problem accepting CDDL code.
The problem would go away if you convinced oracle to change the license or give explicit permission to link ZFS with the linux kernel under the GPL conditions.
Or:
Convinced the linux kernel team to change their license or give explicit permission to link the linux kernel with ZFS under the CDDL conditions.
Or you can blame "GPL", because it obviously was created after CDDL...
It's the other way around.
/s
http://arstechnica.com/tech-policy/2016/05/round-2-of-oracle...
https://en.m.wikipedia.org/wiki/Oracle_America,_Inc._v._Goog....
"The appeals court reversed the district court on the central issue, holding that the "structure, sequence and organization" of an API was copyrightable."
That's a strange way to say relicensing CDDL code under GPL
> A license incompatibility happens when two licenses has each some conditions which are incompatible with each other,
I think it's a bit of a far stretch to say that both licenses are to blame when one license has a so far reaching condition that other code needs to be relicensable under that license.
Which license require that other code needs to be relicensable under its license? this license really means, this license. Modified code is required to be under, and I will repeat myself here, this license. If source code is not under this license, then it is infringing on this license condition and this license will no longer permit redistribution.
This license has a condition, and this license condition makes it incompatible with every other license that has an identical condition.