7 ms·
Licenses only matter to the extent that the resulting product is a "derivative work" of the GPL code. If it's not derivative, then you have no copyright claim t
by jcranmer 6y ago
Licenses only matter to the extent that the resulting product is a "derivative work" of the GPL code. If it's not derivative, then you have no copyright claim that requires the license to permit you to use it.
While the exact nature of when a software project is a "derivative work" of the libraries it depends on is still somewhat of an open legal question, I would be very surprised if anyone were to find that a computer application were a derivative of the OS it runs on. The typical understanding of the industry is essentially a process boundary, and the boundary a system call represents is closer to a process boundary than it is to a library call.
- tyingq 6y agoPerhaps I phrased something odd? We are saying the same thing from my perspective. By "prevents GPL issues", I'm saying the user space code wouldn't need to be GPL.
- jcranmer 6y agoWhat I took away from your message is that you believe that using a syscall directly would cause your application to require GPL licensing, and that glibc being the code that calls the syscall is what prevents it normally.
- tyingq 6y agoSorry, no. I was saying the opposite. I called out glibc to point out that the only linking (as in the linker) was linking to LGPL code.
- radarsat1 6y ago> The typical understanding of the industry is essentially a process boundary, I agree that this is the typical thinking but I've always found it a little silly and arbitrary. It implies that if I write a GPL-licensed library and release it along with a thin wrapper program that gives it a command-line interface, say it does something like a complicated calculation which reads some data and outputs a single number; then someone could come along and write a program that would not work without it, say something that transforms another input format and then passes it to my calculation. As long as that program calls my "library" as a "program" (using "system()" for example) then they are not bound by the GPL, but if they link to my library and call the calculation directly, then all of a sudden they are? This linking vs. process boundary thing always seemed like the wrong way to determine if a program is a derivative work of another. If someone writes a program that does not work without the GPL code, they should be bound by the GPL, regardless of whether it's linked, loaded into the same process, called through the command line, or over the wire. This last one would obviously be controversial, but frankly a lot of companies do hide their use of open source code behind a REST API, and avoid adhering to any particular licenses that way, since they are not "distributing" the software.
- spijdar 6y agoThat goes beyond what most people consider the GPL to cover. There are other licenses with stronger copylefts specifically to cover that last case -- notably, the AGPL. I suspect trying to make the case that GPL's viral copyleft isn't limited to strictly linking but potentially any interaction with it would probably have a chilling effect on the use of GPL code, and this reinterpretation would only reinforce some people's prejudice against the GPL, a la Ballmer's "Linux is cancer" line. Maybe it's the pragmatism in me, but I think it would have a net negative effect long term, unless it managed to flip all of the tables and convince everyone to use all GPL code, instead of making people reject copyleft wholesale.
- radarsat1 6y ago> potentially any interaction with it But that's not what I said. I said programs that do not work without some other program, is, in my opinion, a derivative work. I just don't see how the calling mechanism even plays into that judgement. I do agree that there are other licenses such as the AGPL that try to cover these cases. And arguably the online thing is a whole different ball of wax, because you can talk about software using a service, etc. It really is tricky in that case. But I don't see the reason to distinguish between calling a function via the C stdcall mechanism, vs. "popen" and capturing stdout. It's exactly the same, logically, the only difference are details that imho should not matter for the legal case. Right now, if I release a GPL library, what stops someone from coming along and writing a CLI program that just wraps every function with some textual interface, and including that with their closed-source program? The GPL becomes pretty toothless if it's bypassed so easily.
- qchris 6y agoI'm under the impression that's what the Remote Network Interaction clause of the the Affero GPL license is supposed to do. The "boundary" is then if someone is interacting with the AGPL code at all, so when you use the AGPL-licensed code behind a REST API, even if that's on someone else's server, the use of that code in producing any response to the API request requires publishing the AGPL'ed code/modifications.
- 6y ago