"No non-core Perl modules"
WHAT?
No *way*, man. These modules are made to be used, even
if they are not installed as standard.
OK, let's see the arguments:
- "this being a particularly acute problem for people stuck on Wintel machines"
- "where CPAN does not really shine" - for me, it has worked out
nearly all the time. The main problem for CPAN are firewalls, but even
most firewalls are easily handled by an entry for the http_proxy environment variable.
- 'make' and a compiler are often unavailable - make: go for nmake (available
for free from Microsoft website), compiler: yes, this can be a problem. But most common modules
will be somewhere on the net as binary, compiled by a friendly soul. Or are already available as PPM files
from ActiveState.
- "and PPM is sometimes broken." - for me, it nearly always worked out till now.
The firewall problem is there, of course, but then you can download any PPM by hand
from the ActiveState site with your favorite browser.
- "In
general,if you are contemplating a solution that has to be deployed on more than 2 machines, the repeated installation of the
same module is something you'd really like to avoid. The argument is only stronger if you want to package and distribute
your code to third parties, and you cannot expect to have a perl wizard at the receiving end." - No, no, no. Read the
documentation on the CPAN module Bundle features (e.g., the autobundle command). Just build a bundle
for the things you want to distribute, and distribute that then.
There is a problem here with conflicting versions of modules, but you have
this problem with any library use, and there are solutions to that (see also
this discussion).
- "am I the only person dismayed by the fact that modules using IO::Sockets now try to
perform an install of the entire 5.6?" - No, you're not. That is annoying, for sure.
Reinventing the wheel for something else than educational purposes or big money is a Bad Thing.
Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com
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.