<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using GPL code within proprietory code</title>
	<atom:link href="http://windyroad.org/2006/04/20/using-gpl-code-within-proprietory-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://windyroad.org/2006/04/20/using-gpl-code-within-proprietory-code/</link>
	<description>Extraordinary IT.</description>
	<lastBuildDate>Fri, 16 Jul 2010 18:39:37 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: foo</title>
		<link>http://windyroad.org/2006/04/20/using-gpl-code-within-proprietory-code/comment-page-1/#comment-120190</link>
		<dc:creator>foo</dc:creator>
		<pubDate>Thu, 10 Dec 2009 11:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://howardfamily.id.au/2006/04/20/using-gpl-code-within-proprietory-code/#comment-120190</guid>
		<description>&quot;but copies of the wrapper within the proprietary development team are not&quot;

GPL is a distribution license. As soon as you distribute code that relies on GPL code, you have to distribute it under the GPL. 

It is that simple. 

Your analysis is only correct if you make the wrappers or headers in a generic way, so it can be used by several libraries that could replace the GPL library. Then you are not relying on the GPL library.</description>
		<content:encoded><![CDATA[<p>&#8220;but copies of the wrapper within the proprietary development team are not&#8221;</p>
<p>GPL is a distribution license. As soon as you distribute code that relies on GPL code, you have to distribute it under the GPL. </p>
<p>It is that simple. </p>
<p>Your analysis is only correct if you make the wrappers or headers in a generic way, so it can be used by several libraries that could replace the GPL library. Then you are not relying on the GPL library.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://windyroad.org/2006/04/20/using-gpl-code-within-proprietory-code/comment-page-1/#comment-15333</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Sun, 28 Oct 2007 11:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://howardfamily.id.au/2006/04/20/using-gpl-code-within-proprietory-code/#comment-15333</guid>
		<description>You&#039;re right.  That method is simpler if the GPL and proprietary code are separate.  The suggestion approach above is for when you want to use both in the same program.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right.  That method is simpler if the GPL and proprietary code are separate.  The suggestion approach above is for when you want to use both in the same program.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amr</title>
		<link>http://windyroad.org/2006/04/20/using-gpl-code-within-proprietory-code/comment-page-1/#comment-14998</link>
		<dc:creator>amr</dc:creator>
		<pubDate>Mon, 22 Oct 2007 06:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://howardfamily.id.au/2006/04/20/using-gpl-code-within-proprietory-code/#comment-14998</guid>
		<description>I think there is a way simpler here
http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem</description>
		<content:encoded><![CDATA[<p>I think there is a way simpler here<br />
<a href="http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem" rel="nofollow">http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
