Hyman Rosen <[email protected]> writes: > Even if you were correct (which you are not) that "responsibility" > for executing the program was assigned to the author of the work > rather than to the person running the program, that still fails to > cause any GPL violations, because the person who executes the > program is the owner of the dynamic libraries on his machine, and > the quoted law allows him to _authorize_ making copies essential > to execution.
As long as the program is separately useful without having the dynamic libraries available, and it is sold with the option of this separate usefulness. If not, the linking is an inherent part of putting the program to its intended use, and thus falls under the responsibility of the program creator. > You are simply wrong, and no amount of twisting and spinning is > going to change that. Programs which link dynamically to GPLed > libraries do not become bound by the GPL for that ability. Nothing becomes bound by the GPL. You just have no other option to legally redistribute. But you certainly are free not to redistribute in the first place if your program mandates integration of GPLed code as an integral part of its operation. In that case, you need a license for this integration. -- David Kastrup _______________________________________________ gnu-misc-discuss mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss
