Linked by Thom Holwerda on Tue 7th Sep 2010 21:52 UTC
Permalink for comment 439811
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
More News »
Sponsored Links



Member since:
2007-02-17
I think you meant - it would be like *distributing* a proprietary app linked against the GPL without also distributing your source, or providing the recipient with an offer to obtain the source code along with it.
Even a proprietary application dynamically linked against GPL libraries is OK to distribute, because the proprietary application does not include the GPL libraries. With dynamic linking, the libraries are assumed to be already installed on the end user system, and the proprietary application just calls them. This is fully within the GPL terms ... anyone may simply run the GPL code for any purpose.
A problem only comes about when a proprietary application statically links in a GPL library. This means that the GPL code is now included within the proprietary application. The proprietary application now becomes a derived work according to the definitions of copyright law.
http://en.wikipedia.org/wiki/Derived_work
When it is statically linked the GPL library is included in the proprietary application, the GPL code is a copyright-protected element of an original, previously created first work, and a whole library is indeed a "major element" of the whole work.
According to copyright law, rights to the derived work are in such a case jointly held by the authors of the separate elements that make up the work. The joint owners must come to an agreement about distribution rights with respect to the derived work. If the authors of the proprietary code within the derived work wish to have distribution rights for the derived work, then they must get permission from the authors of all other parts of the derived work which were written by other parties.
The GPL alone does not give such permission. Another license must be sought.
Note that the LGPL license DOES actually give such permission as an exception to the copyleft terms of the GPL. For this very reason, many libraries are licensed under LGPL rather than GPL.
Edited 2010-09-08 04:15 UTC