matija arose from serene meditation and wisely quoth:
To quote perldoc cpan:
The default values defined in the
CPAN/Config.pm file can be overridden in a user specific file:
CPAN/MyConfig.pm. Such a file is best placed in
$HOME/.cpan/CPAN/MyConfig.pm, because $HOME/.cpan is added to the
search path of the CPAN module before the use() or require()
statements.
IIANM there are two situations under which the ~/.cpan/CPAN/MyConfig.pm file and its parent dirs
can come to exist:
- The user is the first one to ever run CPAN.pm on that perl installation (hey, it can happen, on a
not-uncommon single-user workstation setup), or
- The user does what has been cited above, explicitly creating the ~/.cpan/CPAN/MyConfig.pm
file and manually editing the contents to create appropriate settings. In many cases (altho I believe
it is not suggested explicitly in the Fine Documentation for CPAN.pm), the sensible thing to do is to
copy the system-wide Config.pm file from wherever it resides, into one's private dir. Then
"guess" at what the changes needed should be.
In the case (1) above, when CPAN.pm is invoked in the usual manner (on older perls, typically by doing
perl -MCPAN -e shell, and on newer ones by just using the wrapper script named 'cpan' which
does the same thing internally) .. in that case the obligatory (and lengthy, and often confusing for new
perl users) setup interaction will suggest that such a file will be created when the user is done with
the interroga .. er, dialogue.
IMHO this is all a little bit harder than it ought to be. I could describe the points in detail now but
will save it for another time (especially since I've been working on a project that addresses this very
area).
If I am mistaken on any of the factual points (non-subjective, as contrasted with characterizations
like "harder than" or "confusing") I would appreciate being corrected.
Cheers,
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.