My current project has led me to customize a couple of cpan modules. Now that I've found and changed/fixed the modules to suit my purposes, I've realized I need to do something to prevent future versions of the module from breaking me (I do plan to submit my changes to the module author, once they've been cleaned up a bit).

My only idea so far is to copy the modules in question and create a new package using them. I'm not so sure this is a good idea, though...I wonder if I'd run into conflicts with other modules including the 'real' versions of my edited modules, etc.

So, is there an established method for including user-specific modules rather than modules from the /lib or /site/lib paths? How do you go about tracking/protecting changes you've made to modules installed from cpan?


In reply to Customizing cpan modules by jrsimmon

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.