<?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"
	>
<channel>
	<title>Comments on: Lesser GPL</title>
	<atom:link href="http://crschmidt.net/blog/81/lesser-gpl/feed/" rel="self" type="application/rss+xml" />
	<link>http://crschmidt.net/blog/81/lesser-gpl/</link>
	<description>Ramblings of a GIS Hacker</description>
	<pubDate>Thu, 04 Dec 2008 00:48:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Ben Combee</title>
		<link>http://crschmidt.net/blog/81/lesser-gpl/#comment-2160</link>
		<dc:creator>Ben Combee</dc:creator>
		<pubDate>Tue, 21 Jun 2005 05:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/81/lesser-gpl/#comment-2160</guid>
		<description>As mentioned, section 6 only requires that you do one of the actions.  If you use the LGPL'd code as a DLL or shared library, you're covered under section 6b and don't need to produce a written offer for "linking materials".  The 2d section of the license exists to prevent "back-door" extension of a LGPLed library where someone takes the LGPLed code, modifies it to use data or functions in the main non-LGPLed program, then releases it.  It basically says that you can't tightly couple LGPL code with non-free code; you've got to preserve the library's status as a library component that's not exclusive to your program.
</description>
		<content:encoded><![CDATA[<p>As mentioned, section 6 only requires that you do one of the actions.  If you use the LGPL&#8217;d code as a DLL or shared library, you&#8217;re covered under section 6b and don&#8217;t need to produce a written offer for &#8220;linking materials&#8221;.  The 2d section of the license exists to prevent &#8220;back-door&#8221; extension of a LGPLed library where someone takes the LGPLed code, modifies it to use data or functions in the main non-LGPLed program, then releases it.  It basically says that you can&#8217;t tightly couple LGPL code with non-free code; you&#8217;ve got to preserve the library&#8217;s status as a library component that&#8217;s not exclusive to your program.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taral</title>
		<link>http://crschmidt.net/blog/81/lesser-gpl/#comment-2084</link>
		<dc:creator>Taral</dc:creator>
		<pubDate>Thu, 09 Jun 2005 05:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/81/lesser-gpl/#comment-2084</guid>
		<description>Section 6 is disjunctive.</description>
		<content:encoded><![CDATA[<p>Section 6 is disjunctive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Newton</title>
		<link>http://crschmidt.net/blog/81/lesser-gpl/#comment-2083</link>
		<dc:creator>Philip Newton</dc:creator>
		<pubDate>Thu, 09 Jun 2005 05:31:53 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/81/lesser-gpl/#comment-2083</guid>
		<description>It seems to me that the GPL and LGPL are mostly used by people for political reasons, because they want to force software to be as "free", according to their ideology, as possible. Not necessarily because they want their software to be easy to use and modify as possible.

I prefer the BSD licence, myself. (The one without the so-called "obnoxious advertising clause".) The X licence is similar.</description>
		<content:encoded><![CDATA[<p>It seems to me that the GPL and LGPL are mostly used by people for political reasons, because they want to force software to be as &#8220;free&#8221;, according to their ideology, as possible. Not necessarily because they want their software to be easy to use and modify as possible.</p>
<p>I prefer the BSD licence, myself. (The one without the so-called &#8220;obnoxious advertising clause&#8221;.) The X licence is similar.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
