Linux™ applications are not ordinarily considered a GPL derivative. Why then QP™ applications are?
Indeed, past accepted use demonstrates that in the case of Linux™, any application that runs in the User Space is not ordinarily considered a GPL derivative, (provided it uses standard system calls). However, statically linked binaries that run in the Kernel Space are presumed to be Linux™ derivatives. Moreover, binary-only distributions running in either the User Space or the Kernel Space could still be considered GPL derived works. (See the online article “Linux GPL Derivatives in a Nutshell”) In contrast to Linux™, applications based on the QP™ frameworks are always statically linked with the QP™ library. Therefore, QP™ itself must be considered an inseparable “part of a whole”. GPL Section 2 clearly prescribes that in this case “the distribution of the whole must be on the terms of this [GPL] License”.
Related Questions
- We continue to seek intermediates for specialized applications. Which normal alpha olefin derivative offers the greatest versatility in manufacturing new compounds?
- Does the GPL require me to release my extensions, modifications, or applications that use or run on the Pentaho BI Platform within my organization?
- What is a derivative work of open source software?
