<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>CPAN on Brabbel</title>
		<link>https://www.brabbel.net/tags/cpan/</link>
		<description>Recent content in CPAN on Brabbel</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 28 Mar 2010 09:15:25 +0000</lastBuildDate>
		
			<atom:link href="https://www.brabbel.net/tags/cpan/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Package your own Perl for CentOS (or RHEL) as RPM</title>
				<link>https://www.brabbel.net/2010/03/28/package-your-own-perl-for-centos-or-rhel-as-rpm/</link>
				<pubDate>Sun, 28 Mar 2010 09:15:25 +0000</pubDate>
				<guid>https://www.brabbel.net/2010/03/28/package-your-own-perl-for-centos-or-rhel-as-rpm/</guid>
				<description>&lt;p&gt;Of course perl is easy to build and you can&lt;a href=&#34;http://www.brabbel.net/wp/2010/03/build-your-own-fast-perl/&#34;&gt;build your own Perl&lt;/a&gt; is nice, but it needs to be managed on the target host where it is deployed. As internet access to CPAN is not available everywhere (we are talking about enterprise and carrier deployments here) updates need to be managable. At least on a basic level.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Build your own (faster) perl</title>
				<link>https://www.brabbel.net/2010/03/27/build-your-own-fast-perl/</link>
				<pubDate>Sat, 27 Mar 2010 22:57:10 +0000</pubDate>
				<guid>https://www.brabbel.net/2010/03/27/build-your-own-fast-perl/</guid>
				<description>&lt;p&gt;Using the perl that comes with your distribution is usually fine, but it has some limitations. When building a perl for a distribution it needs to be versatile and fit various needs. Therefor ithreads, the perl specific threading implemenation, is enabled there, to allow building modules that require threads to be available.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Add benchmarking tests to MooseX::Log::Log4perl to verify overhead</title>
				<link>https://www.brabbel.net/2009/05/20/add-benchmarking-tests-to-moosexloglog4perl-to-verify-overhead/</link>
				<pubDate>Wed, 20 May 2009 21:27:58 +0000</pubDate>
				<guid>https://www.brabbel.net/2009/05/20/add-benchmarking-tests-to-moosexloglog4perl-to-verify-overhead/</guid>
				<description>&lt;p&gt;After a while I had the chance to get back to &lt;a href=&#34;http://search.cpan.org/perldoc?MooseX::Log::Log4perl&#34;&gt;MooseX::Log::Log4perl&lt;/a&gt;, which is Role (based on &lt;a href=&#34;http://search.cpan.org/perldoc?Moose&#34;&gt;Moose&lt;/a&gt;) that can be easily reused in classes requiring logging functionality.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Bringing logging to Moose with MooseX::Log::Log4perl</title>
				<link>https://www.brabbel.net/2008/07/13/bringing-logging-with-log4perl-to-moose/</link>
				<pubDate>Sun, 13 Jul 2008 21:51:53 +0000</pubDate>
				<guid>https://www.brabbel.net/2008/07/13/bringing-logging-with-log4perl-to-moose/</guid>
				<description>&lt;p&gt;Finally after some playing around and discovering the main concepts behind moose and failing to find a logging role using my favorite logging system log4perl I sat down an did a little coding (it is really just a few lines) and uploaded to CPAN as &lt;a href=&#34;http://search.cpan.org/perldoc?MooseX::Log::Log4perl&#34;&gt;MooseX::Log::Log4perl&lt;/a&gt;.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
