Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Re: Replicate Perl setup

by perlfan (Vicar)
on Dec 12, 2021 at 23:01 UTC ( #11139580=note: print w/replies, xml ) Need Help??


in reply to Replicate Perl setup

> I'm afraid to install the newest modules on the new machine in case there are incompatibilities

Don't be a 'frady cat. No matter what you use an environment - docker, perlbrew, virtualbox, etc - see how far you can get with just a test environment; installing the packages from CPAN or, better, the local package manager. Fix your code where you need to. Once you get that working, your life will be a lot simpler and you'll see how silly being "afraid" actually is. I'd rather be seeing you post questions here regarding the fixing of your code than to enable you to just live in some false sense of fear.

Replies are listed 'Best First'.
Re^2: Replicate Perl setup
by Fletch (Bishop) on Dec 13, 2021 at 13:39 UTC

    One caveat from experience (and if you search through my post history I'm probably a broken record about this):

    Never use the OS' perl and package manager if you don't have 100% control over the OS. With today's container solutions that's less of an issue (since you're more likely to have full control over the image inside), but if you're still on bare metal and at the whim of (say) a central IT department you're going to get bitten at some point. They're going to upgrade your perl and/or packages underneath your application without your knowledge or consent at some point (Murphy sez) and then you're going to be the unfortunate schmuck on the hook to unbreak what they've just broked (because you didn't plan on Foo::Bar suddenly throwing an error because there was an upstream bug your existing code exercised but wasn't handling that's now fixed).

    Always roll and maintain your own application install somewhere you control and use that instead of /usr/bin/perl or whatever. Make sure to shebang everything #!/usr/bin/env perl rather than an explicit path then manage PATH to find what to run (that also allows you to test and migrate to a new version without editing all your scripts).

    The cake is a lie.
    The cake is a lie.
    The cake is a lie.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11139580]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (2)
As of 2022-05-20 23:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you prefer to work remotely?



    Results (76 votes). Check out past polls.

    Notices?