3 ms·
1) This article claims several times that APIs are copyrightable. That is a fairly bold claim to make, and would imply that any libc implementation for linux w
by aidenn0 16y ago
1) This article claims several times that APIs are copyrightable. That is a fairly bold claim to make, and would imply that any libc implementation for linux would need to be licensed by whomever the linux IP holders are. If glibc has not received such a license then it is in violation of the GPL, since it is not released under the GPL.
2) There is the much less strong (and more tenable) claim that functions and macros defined in the headers are copyrightable since they are not a necessary part of interacting with the linux kernel. Google can then become in compliance by removing the offending code and re-implementing it themselves. They could still be liable for damages but...
3) If someone were to sue Google for copyright infringement, they would not be able to compel google to release the code to Bionic under the GPL. That could be part of a settlement, but the most they could hope for in a court is to get Google to stop distributing Bionic, plus receipt of monetary damages.
- cyrus_ 16y agoThe point is that implementations are copyrightable and because Google did not strip out macros and inline functions, it has not simply reimplemented an interface but instead created a derived work.