Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I have found fewer errors after using the FreeBSD-supplied ports of modules. I only use CPAN versions if there aren't FreeBSD versions. Not only do some installs from CPAN not work at all, they don't update the FreeBSD package database properly. 'Package blah has no recorded origin' gets old. :)

Thanks for your thoughts about non-root 'sandbox installs' for testing. I, too, have run into problems using the automated install+test system, especially modules which try to access the external world, and it's necessary to manually install such things as patches to test scripts get overwritten by the CPAN install.

In reply to Re^2: CPAN Wish List by samizdat
in thread CPAN Wish List by tomazos

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.