in reply to Upgrade-proofing overridden subroutines

Runtime is the wrong time to be checking such things. It simply should not be possible to accidently upgrade a dependancy.

If the decision is taken to upgrade one or more third party dependancies, this would usually be a part of a major release, and any breakage as a result of the upgrades would be detected long before this ever got anywhere near a production environment.

If you have to patch a dependancy locally, then it should get an unambiguous new name. Probably moving from the standard /lib path to your /in-house/ path.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In Section Seekers of Perl Wisdom