Alternatively, use PerlBrew to keep several Perl versions. Each version needs its own set of modules (again, in fact, only XS modules need to be different, but if you don't know which these are, just install all of them for each version).

Let's say I have a script that starts as follows:





#!/usr/bin/perl
use strict;
use warnings;

use lib '/home/foo/perl_modules/5.32.1/lib/perl5'
use List::MoreUtils qw(uniq);
[download]





Assume on one machine /usr/bin/perl points to perl version 5.32.1. Also assume the List::MoreUtils module is installed in /home/foo/perl_modules/5.32.1/lib/perl5 using perl 5.32.1.

Now assume on another machine /usr/bin/perl points to perl 5.26.3. Also assume the List::MoreUtils module is installed in /home/foo/perl_modules/5.26.3/lib/perl5 using perl 5.26.3.

Is there a way to manage this such that the script can be run on both machines, each with their respective perl versions, without having to make 2 copies of the script, one for each module path?

If there's only one perl installed on each machine, it makes no sense to include its version into the path. Install the modules into the same path on both the machines and you can use the same script.

If you insist on having the Perl version included in the path and not having Perl configured to search for modules there, you can use something like

use lib '/home/foo/perl_modules/' . substr($^V, 1) . '/lib/perl5';
[download]

But why?

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

Given a directory where perl modules are already installed (ex: /home/user_foo/perl_modules/lib/perl5 from my original message), how do I determine what version of perl was used to install them?

Use Module::Metadata (core) to examine the path:

/usr/bin/perl -MModule::Metadata -le 'print Module::Metadata->find_mod
+ule_by_name("Class::Struct")'
[download]

/System/Library/Perl/5.18/Class/Struct.pm