You ain't gonna like the suggestion but...

You are using a dynamic language, apply the patches dynamically.

That is, c&p the smallest replaceable piece of code that the patch effects, into your code. Apply the patch to the c&p and dynamically replace the sub/method at runtime.

Make that dynamic patch dependant upon the version number of the module you are patching.

Add a testcase and/or in-line test for that will detect if the pre-patched code has been fixed in a later version and if it has, disable the code and issue a warning to the logfile noting that the dynamic patch code can be removed.

  • Document the whole thing very thoroughly, both in the source, and in a separate document that explains:
    1. Why the patch was required--technical reasons.
    2. Why it couldn't be applied in the normal way--polital reasons.
    3. An copy of the email sent to the author requesting the change/addition. Plus any follow-up.

    Get on with the job using the patches and give the document to your supervisor--once you have a sufficient body of work & tests to demonstrate the benefits.

    You should probably include an example of what extra work would be required or what benefits would be lost were the patch not applied.

    Examine what is said, not who speaks.
    Silence betokens consent.
    Love the truth but pardon error.

    In reply to Re: Class::MethodMaker, workplace politics, and patches by BrowserUk
    in thread Class::MethodMaker, workplace politics, and patches by dragonchild

    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.