As others have said, fork the module at a point free of the problems you mention. Then closely examine the current version for anything you can high grade(mining expression for take the good stuff). If you find something worth while, incorporate it into the fork. Document everything and then place in back on CPAN. Given the number of seemingly cloned offerings, I would guess this has happened before. As a fairly weak plan B, contact the original author and see what remedy might follow if any.
--hsm
"Never try to teach a pig to sing...it wastes your time and it annoys the pig."
-
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.
|