Originally posted by k1e0x
View Post
So like it or not my statement is true and yours is false. CDDL gives Sun then Oracle that power.
Originally posted by k1e0x
View Post
Notice point 10 here that your proprietary code has to be special licensed for the conditions in CDDL and the way your code is constructed and build has to be performed particular ways to avoid clashing with CDDL. So you claim CDDL license only effects CDDL labelled code is wrong due to its only clause it ends up effecting your complete project license so you don't breach CDDL.
Yes I can give review after review stating that CDDL is not compatible with lots of Open Source licenses and using CDDL parts come restrictive on your proprietary code license that you mix with CDDL. CDDL demands that any over license does not alter it source code terms.
Not incorrect that only retains to it own code if you use CDDL the wrong way in the USA it comes viral same with a lot of other Licenses that you might think harmless. CDDL applied to header files with macros and inlines it is now viral at this point once you use those macros and inlines in other no CDDL files. There is a ruling in the USA that macros and inline in header files are not classed as API define instead classed as active code. So you cannot copy them as is from header files and using them in your code means you code has to conform to the license of the header file. This is a bingo surprise of the USA counts the way they ruled that using macros and inlines was part of the source file using them as well as the header they came from.
Please note the USA ruling effects stuff like MIT licensed header files as well this is not as big of problem with a lot of license stuff as with MIT does not say only its terms. Funny enough using MIT header files with a CDDL file equals trouble.
GPL define of derivative work in fact stops this evil if the header is GPL as long as your code is true independent work. CDDL does not have clause to deal with how USA courts have ruled. In fact a lot of the older licenses like BSD licenses don't have clauses preventing inline and macro causing clash based on how the USA court ruled.
Originally posted by k1e0x
View Post
Originally posted by k1e0x
View Post
Zol follows the Nvidia and OS X dtrace method of legal arms length to a point. There are questions on some of the overlaps in Zol that they may not have kept all the separations as clean as they need to be..
Originally posted by k1e0x
View Post
The price from wrapping form one API to another API is always compatibly problems. Yes lets make an invalid excuses for not using the common core in the Linux kernel claiming is all broken. When it you legally cannot use it and end up abstracted and applying solaris kernel methods to Linux kernel and watching everything go wrong. Round peg square hole.
The reality here is the btrfs guys have better chance of working properly on Linux than ZFS does while CDDL license clause exists causing the Linux kernel to be abstracted to pretend to be another OS. OS X bugs in dtrace come from the same problem of abstracting the OS X kernel to solaris structures to avoid CDDL issue.
CDDL stuff being broken on non CDDL kernel is quite common it is not Linux unique its due to the hoops the CDDL license causes.
Originally posted by k1e0x
View Post
Basically all this fear/panic crap claim by you is basically you sticking you head in the sand and not using a single legal review to see where the state of affairs really is.
I have used a few legal reviews to base my point of view on. You have not provided one cite backing your point of view. Instead I am meant to take you at faith.
k1e0x so far in the camp of supportable claims about CDDL license or GPL license you have made is zero. You have fairly much got everything wrong. It really about time you spend some time reading the legal reviews and learn that CDDL is a problem child. CDDL can only be used with licenses be it open source or closed source that contain particular clauses/mode of operation and be legally safe. Freebsd license itself is not one of them. There is a common error about CDDL that you can license binaries how ever you like and that is false as well. Binary license over something containing CDDL cannot contain any clause about source that would over ride the CDDL parts terms.
[url]https://opensource.org/licenses/MIT[\url]
The reality of now bad CDDL is that MIT license is technically incompatible with CDDL. Because including MIT work in a CDDL file would require adding MIT terms to the file that the CDDL license absolutely forbids.
There is a legal review out there covering why different licenses should not be mixed with MIT licensed works.
Reality here GPL is hard to get alone with. CDDL is even harder. BSD and MIT licensed works are also not exactly fun due to different USA court rulings there is a list of things you have to watch out for.
Comment