in reply to Wrong + Right = Even Worse

> Originally, the full paths were used in require, which constituted one of the obstacles to run the project locally.

You can also put a coderref-hook in front of @INC to catch and redirect all do and require.

You can apply the same technique for a life monitoring of the dependencies by logging the caller. This might help you migrate the projects.

Not sure about CPAN modules doing this, see Re: How to use @INC coderef hooks (perldoc wrong) and linked threads for demos.

Cheers Rolf

( addicted to the Perl Programming Language)

Replies are listed 'Best First'.
Re^2: Wrong + Right = Even Worse (@INC sub)
by tye (Sage) on Apr 04, 2014 at 15:52 UTC
    You can also put a coderref-hook in front of @INC to catch and redirect all do and require.

    Not "all". It won't catch a require for an already-loaded module.

    - tye        

[reply]
      One would need a private shadow %MY_INC within the catch-sub to handle it and keeping %INC clean.

      I'm aware this would cause problems with code accessing %INC directly, but I somehow doubt this legacy code base ever attempts to do such things.

      IMHO good enough for debugging.

      Cheers Rolf

      ( addicted to the Perl Programming Language)

[reply]

In Section Meditations