For me, it depends.
Most of the time, I use the CPAN shell. Especially for a module that I'll only want on my machine for a limited amount of time. I've got my environment all set up with a ~/.cpan/CPAN/MyConfig.pm to build and install modules in a ~/.perl subdirectory, and corresponding environment variables so that my one-off scripts use it just fine. I don't even need to be root. Cool.
Sometimes the module I want is already packaged in the Debian distribution. So, I apt-get it instead. Even cooler.
Sometimes the module I want isn't packaged by Debian, but I need it enough that I want to install it properly so that all users of my system will have access to it. For that, I make a .deb out of it myself with
dh-make-perl. Very cool.
What it all comes down to is, I've got way too much free-time.
--
jwest
-><- -><- -><- -><- -><-
All things are Perfect
To every last Flaw
And bound in accord
With Eris's Law
- HBT; The Book of Advice, 1:7
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.