My only beef with the port system, which is not particular to macports, but to any packaging manager, is how you manage the multiple libraries of available modules. If you use port, you should probably use it for common modules too (and there are many, like p5-www-mechanize).

If it's not on the macports list (and there are many), then it feels ugly to try to use CPAN to manage a second packaging layer on top of that, and not know whether the module you're requesting will end up building a constellation of modules that are unproven on your platform.

The last alternative is to go through the dependency hell yourself in your own local PERLLIB directory, which is only slightly more unsavory and has the same pitfalls.

When I did more development on Red Hat Linux, the same deal applied to their repository, but I got familiar with how to repackage most CPAN modules with cpanflute at the time, so I could at least work with one installation library path. With macports, I'm not familiar with this route: how to make a port file for a CPAN module, so it would install safely in the same tree with other port-installed p5-* modules.

--
[ e d @ h a l l e y . c c ]

In reply to Re^2: Reinstalling perl from scratch on OS X by halley
in thread Reinstalling perl from scratch on OS X by dhosek

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.