<?xml version="1.0" encoding="windows-1252"?>
<node id="823144" title="Installing Modules" created="2010-02-14 11:38:46" updated="2010-02-14 11:38:46">
<type id="115">
perlquestion</type>
<author id="704000">
Xiong</author>
<data>
<field name="doctext">
&lt;p&gt;
(Note: I'm running Ubuntu 9.10 on i386.) 
&lt;/p&gt;
&lt;p&gt;
I've installed a great many modules from CPAN using &lt;c&gt;sudo cpan&lt;/c&gt;. I've installed a great many &lt;c&gt;.deb&lt;/c&gt; packages using appropriate methods, some of which seem to contain Perl modules, too. I've also run into a spot of trouble (although I can't swear &lt;c&gt;cpan&lt;/c&gt; has a thing to do with it) with conflicts between modules installed from these different sources. (Synaptic itself seems to rely on &lt;c&gt;XML::SAX&lt;/c&gt;, for example.)
&lt;/p&gt;
&lt;p&gt;
Various forum posts of dubious reliability and a buddy of mine suggest I never install any modules with &lt;c&gt;cpan&lt;/c&gt; unless there is no alternative; rather, prefer to install only using Synaptic, &lt;c&gt;apt-get&lt;/c&gt;, and friends. 
&lt;/p&gt;
&lt;p&gt;
What say the Monks?
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Update:&lt;/b&gt; Great comments, thank you. I will leave the system &lt;c&gt;perl&lt;/c&gt; and its libraries alone; if I install an application that requires modules, I'll let Synaptic take care of the dependencies. I'll compile a distinct development &lt;c&gt;perl&lt;/c&gt; somewhere else and use &lt;c&gt;cpan&lt;/c&gt; to install whatever I like there. I'll use the opportunity to consider different compilation flags, too. 
&lt;/p&gt;</field>
</data>
</node>
