just make a note of it in my own docs and go on?

Bump the version number and make a note in your code/Makefile.PL

If you have a CPAN account, you should release a patched version and save the next monk-ey from having to go to rt, find patch, download patch, apply patch, deploy patch ... they can just  cpan BOTFX/AppConfig-1.6601.tar.gz and be done with it

Beyond that, there are numerous bug reports for that module, seems a bit dis-concerting for something that is included as part of CORE... CORE...

Where do you get that idea?

$ corelist AppConfig

Data for 2013-11-20
AppConfig was not in CORE (or so I think)

[download]

In reply to Re: Best way to deal with a bug in a CORE Module (release patched version) by Anonymous Monk
in thread Best way to deal with a bug in a CORE Module by boftx

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.