in reply to Change Namespace of Package

In addition to what haukex said, you could also set up different Perl installations for each version (ie. install a specific version of Perl, clone it, install v7 on one instance, v8 on the second instance, and switch between them when testing/working with one version or the other). If the user-facing APIs haven't changed between versions of InfoBlox, your scripts would work seamlessly between Perl instances. Otherwise, you'd simply have to either have an argument that determines which version you want to operate against, or just have separate scripts per version.

It would help if you could let us know what Operating System you're running, along with an example script showing how you're using the module.

A briefing of your development practices would also be beneficial here; for example, do you have to make changes to your scripts in order to use the differing versions of this module?

Replies are listed 'Best First'.
Re^2: Change Namespace of Package
by elliott9 (Novice) on Sep 14, 2019 at 22:08 UTC
    A second perl instance was something I had considered before I made this post but it seemed extreme so I thought I would ask for help first. I am glad I did because what haukex wrote fixed me right up. I am running to different scripts depending which server I need to reach out to. Thanks for the help. To answer your other questions my production environment is Red Hat but once I started messing around with the initial package I needed a development environment to play with. I ended up installing Strawberry Perl on my Windows workstation for that purpose and while it wasn't ideal, it worked well enough.