in reply to Force reinstall on NFS via CPAN::install (or other method)?

Binary compatibility is an issue between versions. I'd advise against trying to support multiple versions of perl on one directory of modules. This will make life difficult. Either install perl manually in a directory other than your system perl, and just install your modules as normal, or use a tool like perlbrew if you want to manage multiple versions of perl on the same system. Also reinstall all modules on new perl, cpan with -a.

Replies are listed 'Best First'.
Re^2: Force reinstall on NFS via CPAN::install (or other method)?
by loris (Hermit) on Dec 21, 2017 at 12:35 UTC

    I do realise that my original idea was a bad one. I had assumed that Perl sorts out the version- and architecture specific bits of modules into the various separate subdirectories which seem to exist. Obviously not. However, my question is how to reinstall just those modules for 5.10 on the NFS share?

[reply]
      cpan -f -i Module::Name

      or with cpanm:

      cpanm --reinstall Module::Name Other::Module

      While specifying your local::lib config.

[reply]
[d/l]
[select]
      > I had assumed that Perl sorts out the version- and architecture specific bits of modules ... Obviously not.

      Obviously, as you told it where to install them. Normally, custom built perl stores the libraries into its own site_perl directory and everything works.

      ($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

      [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom