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?
-
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.
|