http://qs321.pair.com?node_id=878771


in reply to Module development: concurrent versions (Updated)

Probably by using PERL5LIB environment variable to first point to the old version of the module, then the new one

Or -I switch to achieve the same as the above

Or the version control idea could work too, use git ( or some such ) to place the perl installation under version control, then you could have the old version on one branch and the new on another branch and just checkout the different branches as you test.

  • Comment on Re: Module development: concurrent versions (Updated)