[Cialug] Tasks for learning shell scripting

[Don Ellis]

A while back, the StL Perlmongers presentation was on using other
package managers to manage the perl libraries.

The premise was that pretty much any package in CPAN is also available
in yum/rpm/apt, but that the Linux PMs work better/more smoothly than
CPAN, and keep perl packages in the Linux PM world. I think it's a
simple translation from the CPAN name to the yum/rpm/apt version of
the name, and when I've tried it, it has worked great.

--Don Ellis


On Wed, Sep 29, 2010 at 11:00 AM, Paul Gray <gray at cs.uni.edu> wrote:
> On 09/29/2010 10:46 AM, Daniel A. Ramaley wrote:
>> On 2010-09-29 at 10:34:34, Josh More wrote:
>>> More seriously, Perl's biggest drawback is CPAN.
>>
>> Is "drawback" really the word you were looking for?
>>
>> I think Perl's biggest strength is CPAN, actually. That's what keeps me
>> programming in Perl and not some other language. For almost anything
>> that i don't feel like coding myself, there's a module to do it for me.
>> And for the few modules i want to use that aren't available as a Debian
>> package, CPAN makes it trivial to install them and keep them updated.
>>
>
> ... and thereby risk the loss of integrity of your Debian package management
> system (unless you backtrack and appropriately mark the Debian packages as
> "hold", and remember to uninstall the CPAN module when you release the package
> hold, and ...yadda yadda - but not in the Seinfeld sense).
>
> So I wouldn't use the term "drawback" either. For me, CPAN is a *liability*
> because it puts Perl functionality above Debian package management.
>
> But admittedly, that's likely just me.
>
> --
> Paul Gray                                         -o)
> 314 East Gym, Dept. of Computer Science           /\\
> University of Northern Iowa                      _\_V
>  Message void if penguin violated ...  Don't mess with the penguin
>  No one says, "Hey, I can't read that ASCII attachment ya sent me."