Oracle runs on Linux. That means they must have linked in headers to GPL'd code, which they are therefore loading dynamically.
Now although it's obvious that Vidomi's only reason for their dynamic linking architecture is to avoid having to GPL their code, there is no language in the GPL to explicate the difference between Oracle and Vidomi.
You might say, "It's obvious that Vidomi's dynamic linking architecture exists solely to avoid having to GPL their code," and I think you'd be correct, but that doesn't change the fact that the GPL, as it is written, is no less fulfilled by Vidomi than it is by Oracle.
I'll bet the FSF doesn't even take this case to court, let alone win.
The GPL will not withstand legal scrutiny until it includes explicit language about what forms of software/process interaction are considered to make a work derivative.
Slashdot Mirror
Oracle runs on Linux. That means they must have linked in headers to GPL'd code, which they are therefore loading dynamically.
Now although it's obvious that Vidomi's only reason for their dynamic linking architecture is to avoid having to GPL their code, there is no language in the GPL to explicate the difference between Oracle and Vidomi.
You might say, "It's obvious that Vidomi's dynamic linking architecture exists solely to avoid having to GPL their code," and I think you'd be correct, but that doesn't change the fact that the GPL, as it is written, is no less fulfilled by Vidomi than it is by Oracle.
I'll bet the FSF doesn't even take this case to court, let alone win.
The GPL will not withstand legal scrutiny until it includes explicit language about what forms of software/process interaction are considered to make a work derivative.
- fd
IANAL, TINLA, YMMV, HAND