On Tue, Dec 24, 2013 at 12:02:31PM +0100, Carlos Alberto Lopez Perez wrote: > About the system library exception, this is what the GPL FAQ tells: > Q: Can I link a GPL program with a proprietary system library? > A: Both versions of the GPL have an exception to their copyleft, > commonly called the system library exception. If the GPL-incompatible > libraries you want to use meet the criteria for a system library, then > you don't have to do anything special to use them; the requirement to > distribute source code for the whole program does not include those > libraries, even if you distribute a linked executable containing them. > The criteria for what counts as a "system library" vary between > different versions of the GPL. GPLv3 explicitly defines "System > Libraries" in section 1, to exclude it from the definition of > "Corresponding Source." GPLv2 deals with this issue slightly > differently, near the end of section 3. > https://www.gnu.org/licenses/gpl-faq.html#SystemLibraryException The GPL FAQ has historically failed to cover various nuances of the license that affect OS distributors. The FAQ is not the license. The FAQ previously gave uselessly unclear advice around GPL plugins, as well. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature