If what the code is currently doing is not a problem, then you don't have a problem, do you?

I think you misstated something here. I guess you are trying stress your vexation anticipating his fix clobbering your fix and that that future is not coming soon enough. This indicates a basic trust issue with the code you are using. You imply the module doesn't have versions, if it does, don't waste time generalizing your solution. Instead, for the modules you care about, report the bug of lack of versions. You need to be able to divine the version of things to maintain the control/quality/efficiency standards which you seek.

Within the limitations he describes, adrianh's solution is suited to your problem.

What are the problems with forking? If you have hope that the author will be back someday, you can do it quietly by renaming the packages and distributing them within your distribution. So long as you hope, you treat the code as if it were still under its author's care. If he wakes up or comes back or finds time, you can refactor the code easily at your convenience. If it turns out the code is abandoned, it will be nice that you kept it alive.

Be well,
rir

In reply to Re^5: Upgrade-proofing overridden subroutines by rir
in thread Upgrade-proofing overridden subroutines by Ovid

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.