I prefer to manage Red Hat with RPM-- the first step when I find a new module I'd like to install is to see if there's an RPM of that module. Here's a strategy:
(1) Do an (up2date install perl-Crypt-RSA) to see if Red Hat Network already has it packaged.
(2) Google for "perl-Crypt-RSA rpm" for some ideas if this is commonly packaged by third-parties.
(3) Download the CPAN tarball and use a cpan2rpm converter script to make a .src.rpm for it. This .src.rpm will have all of the build-requires fields properly set. Then rebuild to get the .noarch.rpm or .i386.rpm or whatever.
Every once in a while, someone proposes an all-CPAN RPM repository, but I've yet to see anyone stick to such a project. Since Red Hat is a python-favoring distribution, this is not a big surprise.
This may seem like a pain to manage, but it makes your Perl configuration easily duplicatable on other machines, and eases your management of upgrades of the whole system.
--
[ e d @ h a l l e y . c c ]
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.