Perl 5.14 ad default, and Irssi to use it

[Puneet Kishor]

On Jan 16, 2012, at 6:56 PM, Ryan Schmidt wrote:

> 
> On Jan 16, 2012, at 18:54, Puneet Kishor wrote:
> 
>> 
>> On Jan 16, 2012, at 6:45 PM, Ryan Schmidt wrote:
>> 
>>> We recommend you do not use cpan. 
>> 
>> 
>> Why not? I have been using `cpanm` to install all my Perl modules, and have even compiled one from scratch (the `perl Makefile.PL && make && sudo make install` dance) and have not experienced any problem thus far.
>> 
>> So, I am curious as to why the recommendation to not use cpan to install modules.
> 
> Because I was under the impression that cpan would install things to the same place that MacPorts would install them, and thus cause a conflict.
> 
> 


yes, you are correct that cpan and macports would install to the same location, but there really should be no conflict as long as the modules are built correctly. They are just two different ways to install modules to the same location. The only problem I can thing of is that cpan (or, in my case, cpanm) might overwrite a macports installed module, and, assuming that macports maintains some sort of a "receipts" system, it might get confused, but that also shouldn't occur. Macports would really never know the difference... it would continue to think that package foo is as installed by it even though it might be a new version installed by cpan(m).

I recently installed PDL 2.4.6 using macports and then upgraded it to PDL 2.4.9 by downloading the PDL source code and doing the perl Makefile.PL bit... it works just fine. In fact, if I recall correctly, the only part of perl that I installed using macports is Perl 5.14.1. Every single other module installed by me has been with the help of cpanminus, and it all just works.

I hope I don't get bit in the butt, but so far so good.

--
Puneet Kishor