title: How do I handle installing scripts in Perl modules with multiple versions of Perl?
body: <p>I don't think that this is a duplicate question. This is specifically about scripts that come with Perl modules.</p>
  <p>Typically, when installing multiple Perl versions, you can have the perl executable tagged with a version number (<code>perl5.32</code>) so that they can all sit side by side in <code>/whatever/bin</code>. I need to do the same for scripts that come with modules. Example: <code>perltidy</code>. So:</p>
  <p>Is there a setting I can throw on the config when I build perl that will automagically [sic] create 'versionated' script names?</p>
  <p>Or, is there something I can set when I call <code>perl Makefile.PL</code> or <code>perl Build.PL</code> when I am building the script to make 'versionated' script names?</p>
  <p>Yes, there are <code>plenv</code> and <code>perlbrew</code>, but I don't want to use those on the production side, yet there will be a period of time on my production machines when both versions will exist. I will be migrating programs over time; I will not be &quot;big-banging&quot; a cut over to a new version one night.</p>