I really recommend reading haukex's post again and taking his advice to heart. Besides security concerns, changing directories in code is, to me, code smell. Lots of Perl devs, including me, work on OS X and it doesn't seem to have any more gotchas than any other *nix. And like any other *nix, I highly recommend against tampering with the System perl. That includes installing new modules. Plain Perl will likely be fine but once you mess with the wrong C-based module/lib, you may hose your entire installation. perlbrew and local::lib are a couple of ways to make it easier to have it all.

In reply to Re^2: Config::Tiny croaks at runtime, not in debugger by Your Mother
in thread Config::Tiny croaks at runtime, not in debugger by xavier8854

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.