27 ms·
What's the problem with using GPL software if you don't want to change it?
by k__ 9y ago
What's the problem with using GPL software if you don't want to change it?
- yorwba 9y agoAFAIK, software for the BSDs is usually maintained in-tree, and patched to integrate with the rest of the distribution. I don't think including GPL-licensed software would be compatible with the BSD license of the overall project. That doesn't mean you can't use anything GPL, just that it can't become part of the system.
- _delirium 9y agoAll the BSDs have traditionally included GPL'd software in the base system, so I don't think many people share this view (it's a possible interpretation of the GPL, but not a common one). As one major example: every BSD until recently included gcc in-tree, and OpenBSD and NetBSD still do.
- loeg 9y agoFreeBSD sees this as a necessary evil and aims to move to zero GPL code in base, eventually (when ports GCC works well enough for 2nd tier architectures and Clang/ias / elftoolchain works well enough for 1st tier architectures).
- user5994461 9y agoYou can't use GPL code in non GPL software.
- perlgeek 9y agoI thought you can't link to GPL Software in non-GPL software? Shipping an unmodified copy of git and calling it should be fine even in proprietary code, no?
- marcoperaza 9y agoThis is an open question. The GPL itself does not define what constitutes a derivative work. The FSF does, however, promote the view that linking does create a derivative work, while simply calling an external binary in usual cases does not. But that can't function as a hard rule. Because I could just make a wrapper binary that handles all of the scenarios I need a GPL'd library for, and then call my wrapper executable from my proprietary code.
- jahewson 9y ago> Because I could just make a wrapper binary that handles all of the scenarios I need a GPL'd library for, and then call my wrapper executable from my proprietary code. Yes, you can literally do this. It's not a derived work because your code is entirely independent of the GPL'd code and the GPL can't possibly cover code that you wrote independently. Simply interacting with some external GPL'd program does not expose your code to any GPL requirements.
- marcoperaza 9y agoYou can't just work around the GPL by placing a command-line interface as a shim between your code and the function call interface of the GPL'd library. I'm talking about a contrived binary that just calls library functions, forwarding command line parameters to the arguments of that function as necessary.
- toast0 9y agoWho says they don't want to change it? Integration with OpenBSD pledge or FreeBSD capsicum could be useful.