<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://lions.teledyn.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title> - Distros Violate the GPL? - Comments</title>
 <link>http://lions.teledyn.com/node/568</link>
 <description>Comments for &quot;Distros Violate the GPL?&quot;</description>
 <language>en</language>
<item>
 <title>Distros Violate the GPL?</title>
 <link>http://lions.teledyn.com/node/568</link>
 <description>&lt;p&gt;Are the Linux distributions violating the GPL?  Sends a shiver down your spine, don&#039;t it. &lt;i&gt;Ce n&#039;est pas possible!&lt;/i&gt; Perhaps unthinkable, but nonetheless, it may be true, at least true for that handful of crews using a package manager to distribute their distro-harmonized binary-format bundles.&lt;/p&gt;
&lt;p&gt;Allow me to explain ...&lt;/p&gt;
&lt;p&gt;First off, so there&#039;s no mistake, let&#039;s establish our ground rules and quote from the source, from the GPL2 Terms and Conditions, section&amp;nbsp;3:&lt;br /&gt;
&lt;blockquote&gt;&lt;cite&gt;&quot;... The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.&quot;&lt;/cite&gt;&lt;br /&gt;
&lt;small&gt;&lt;i&gt;&lt;a href=&quot;http://www.gnu.org/licenses/gpl.html&quot;&gt;GNU General Public License version 2&lt;/a&gt;&lt;/i&gt;&lt;/small&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Ok, now, this says that if you distribute software, &lt;em&gt;you must make the source available for free&lt;/em&gt;.  &lt;/p&gt;
&lt;p&gt;That means the source of the &lt;u&gt;binary&lt;/u&gt; you are redistributing, including any patches you may have applied, the source code for the software you actually bundle.&lt;/p&gt;
&lt;p&gt;Now here&#039;s where it maybe gets a little fuzzy, fuzzy enough for vendors to retain their proprietary edge while remaining inside the letter of the law if not it&#039;s spirit: C/C++ code is source, no question, and &lt;code&gt;.h&lt;/code&gt; header files are also indisputably source code.  So are &lt;code&gt;Makefile&lt;/code&gt; and even &lt;code&gt;configure.in&lt;/code&gt; and &lt;code&gt;Makefile.in&lt;/code&gt; and herein the problem ... &lt;em&gt;what about &lt;code&gt;config.status&lt;/code&gt;?&lt;/em&gt;&lt;/p&gt;
</description>
 <comments>http://lions.teledyn.com/node/568#comments</comments>
 <category domain="http://lions.teledyn.com/taxonomy/term/11">GPL</category>
 <category domain="http://lions.teledyn.com/taxonomy/term/49">Linux</category>
 <pubDate>Thu, 27 Jan 2005 10:42:01 -0500</pubDate>
 <dc:creator>garym</dc:creator>
 <guid isPermaLink="false">568 at http://lions.teledyn.com</guid>
</item>
</channel>
</rss>
