To view parent comment, click here.
To read all comments associated with this story, please click here.
>Distributing a GPL product which requires an non GPL tool to build, which is not a standard system tool usually distributed with operating systems is a GPL violation.
No it isn't even the FSF doesn't say this, though they do recommend to find another solution
http://www.gnu.org/philosophy/java-trap.html
"http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377109"
Thank you for the link. However, the discussion seems to center around the fact that the GPL software and the CDDL build system where distributed together (i.e., more than "mere aggregation"). It was not an argument about linking GPL software to non-GPL software or GPL software with non-GPL dependecies. For more information, see the Java Trap link posted by progster and the following items from the GPL FAQ:
http://www.gnu.org/licenses/gpl-faq.html#FSWithNFLibs
http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs
By my understanding, copyright holders can license their source under any license they see fit. Whether that work is valuable or reasonably redistributable by a third party is a different matter. In fact, it may be strictly undistributable in binary form (putting it off-limits to a distro like Debian). But since the source is GPL, a third party can take the valuable parts and toss the rest, which seems to be exactly the outcome of the cdrtools/cdrkit case.




Member since:
2006-05-14
> I'm not familiar with this event, so could you please
> give some references?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377109
> Your description doesn't sound like a GPL violation per
> se, but Debian often adopts a stricter definition of
> "free".
No, this was discussed strictly as a GPL violation. The debian fork of cdrtools, cdrkit, was also a result of this problem.
Distributing a GPL product which requires an non GPL tool to build, which is not a standard system tool usually distributed with operating systems is a GPL violation.
If this werent a GPL violation it would mean that you could distribute GPL programs that only work with additional tools, which could be proprietary and require a fee to use. The GPL prevents such a scenario.
It is a GPL violation of the nvidia wrapper if this wrapper does not perform some function or is not able to build without this binary blob. In this case they are not allowed to distribute it under the GPL but they do.