<?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: Packages, modules and distributions</title>
	<atom:link href="http://www.dagolden.com/index.php/308/packages-modules-and-distributions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/</link>
	<description>Whatever comes to mind</description>
	<lastBuildDate>Mon, 23 Jan 2012 03:43:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Version numbers should be boring</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-296</link>
		<dc:creator>Version numbers should be boring</dc:creator>
		<pubDate>Thu, 06 Aug 2009 01:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-296</guid>
		<description>[...] on CPAN also have version numbers. These are specified as part of the filename. (See a prior article for a formal definition of modules and [...]</description>
		<content:encoded><![CDATA[<p>[...] on CPAN also have version numbers. These are specified as part of the filename. (See a prior article for a formal definition of modules and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BenRifkah</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-245</link>
		<dc:creator>BenRifkah</dc:creator>
		<pubDate>Wed, 22 Jul 2009 19:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-245</guid>
		<description>These are all good definitions of the terms although I have one point that may appear to be minor at first but may make a difference if these definitions are to be used when considering tool chain modifications.

In your module definition you mention that &quot;Compiling the module should return a true value.&quot;  I think that what you&#039;re getting at is that &quot;use&quot;ing the module should not fail with a &quot;foo.pm did not return a true value&quot; exception.  However, one could interpret this to mean that &quot;perl -c foo.pm&quot; returns true.  perl -c will return true if your file doesn&#039;t return true and doesn&#039;t contain any compilation errors.  Clarifying this point can potentially avoid some confusion.</description>
		<content:encoded><![CDATA[<p>These are all good definitions of the terms although I have one point that may appear to be minor at first but may make a difference if these definitions are to be used when considering tool chain modifications.</p>
<p>In your module definition you mention that "Compiling the module should return a true value."  I think that what you're getting at is that "use"ing the module should not fail with a "foo.pm did not return a true value" exception.  However, one could interpret this to mean that "perl -c foo.pm" returns true.  perl -c will return true if your file doesn't return true and doesn't contain any compilation errors.  Clarifying this point can potentially avoid some confusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-244</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 22 Jul 2009 14:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-244</guid>
		<description>Really excellent post. Thanks, David. This information belongs in the Perl 5 wiki if it&#039;s not there already.

Here&#039;s a similar blog post -- but for Python -- which you might find interesting: http://blog.ianbicking.org/2008/12/14/a-few-corrections-to-on-packaging/

Also, does Perl 6 use the same terms (above) as Perl 5?</description>
		<content:encoded><![CDATA[<p>Really excellent post. Thanks, David. This information belongs in the Perl 5 wiki if it's not there already.</p>
<p>Here's a similar blog post -- but for Python -- which you might find interesting: <a href="http://blog.ianbicking.org/2008/12/14/a-few-corrections-to-on-packaging/" rel="nofollow">http://blog.ianbicking.org/2008/12/14/a-few-corrections-to-on-packaging/</a></p>
<p>Also, does Perl 6 use the same terms (above) as Perl 5?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-242</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 21 Jul 2009 01:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-242</guid>
		<description>That&#039;s a good point.  I did think to say &#039;zero or more&#039; modules, but it&#039;s good to be explicit about the other uses for distributions.</description>
		<content:encoded><![CDATA[<p>That's a good point.  I did think to say 'zero or more' modules, but it's good to be explicit about the other uses for distributions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fREW Schmidt</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-241</link>
		<dc:creator>fREW Schmidt</dc:creator>
		<pubDate>Mon, 20 Jul 2009 23:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-241</guid>
		<description>I&#039;d also mention that some dist&#039;s on CPAN may have tools but not modules, or at least the modules may not be for public consumption but only for the dist&#039;s executable files.</description>
		<content:encoded><![CDATA[<p>I'd also mention that some dist's on CPAN may have tools but not modules, or at least the modules may not be for public consumption but only for the dist's executable files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hdp</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-240</link>
		<dc:creator>hdp</dc:creator>
		<pubDate>Mon, 20 Jul 2009 13:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-240</guid>
		<description>I agree with all of the above, but have nothing substantial to add.  Well said.</description>
		<content:encoded><![CDATA[<p>I agree with all of the above, but have nothing substantial to add.  Well said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-239</link>
		<dc:creator>david</dc:creator>
		<pubDate>Mon, 20 Jul 2009 11:10:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-239</guid>
		<description>That&#039;s a great example!</description>
		<content:encoded><![CDATA[<p>That's a great example!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Heaney</title>
		<link>http://www.dagolden.com/index.php/308/packages-modules-and-distributions/comment-page-1/#comment-237</link>
		<dc:creator>Tim Heaney</dc:creator>
		<pubDate>Mon, 20 Jul 2009 10:30:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dagolden.com/?p=308#comment-237</guid>
		<description>It&#039;s good to define these terms too, because they are so overloaded. For example, to install a &lt;strong&gt;module&lt;/strong&gt;, I might use the &lt;strong&gt;package&lt;/strong&gt; manager from my &lt;strong&gt;distribution&lt;/strong&gt;

&lt;code&gt;$ sudo apt-get install libmodule-build-perl&lt;/code&gt;

That&#039;s not CPAN, but it&#039;s close enough in context to add confusion, if we&#039;re not careful.</description>
		<content:encoded><![CDATA[<p>It's good to define these terms too, because they are so overloaded. For example, to install a <strong>module</strong>, I might use the <strong>package</strong> manager from my <strong>distribution</strong></p>
<p><code>$ sudo apt-get install libmodule-build-perl</code></p>
<p>That's not CPAN, but it's close enough in context to add confusion, if we're not careful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

