That's not what I want. I am supporting 3 different platforms with this installation of Perl and associated modules. I am using a single module directory and a distinct script dir for each platform. My CPANPLUS config looks like this:

    makemakerflags            'PREFIX=/home/perl/lib INSTALLSCRIPT=/home/perl/lib/x86_64-bin'

In fact, it looks like this in the actual Config.pm file:

$conf->set_conf( makemakerflags => 'PREFIX=/home/perl/lib INSTALLSCRIPT=' .$ENV{MY_PERL_DIR} );

Where MY_PERL_DIR is set based on the architecture of the platform on which I run CPANPLUS, so the value of INSTALLSCRIPT always points to the directory that shold contain the executables for the current platform.

PREFIX is working as expected, but INSTALLSCRIPT isn't.

Try adding INSTALLBIN:

makemakerflags  'PREFIX=/home/perl/lib INSTALLBIN=/home/perl/lib/x86_6
+4-bin INSTALLSCRIPT=/home/perl/lib/x86_64-bin'
[download]

No go. INSTALLBIN doesn't help. Still goes into the bin dir under the PREFIX dir.

I suspect that it's a packaging mistake, not a MakeMaker problem.

...so I followed up on that and, for instance in Perl::Tidy, the script is specified as EXE_SCRIPT:

EXE_FILES => ['bin/perltidy'],

From the MakeMaker man page:

EXE_FILES

Ref to array of executable files. The files will be copied to the INST_SCRIPT directory. Make realclean will delete them from there again.

If your executables start with something like #!perl or #!/usr/bin/perl MakeMaker will change this to the path of the perl 'Makefile.PL' was invoked with so the programs will be sure to run properly even if perl is not in /usr/bin/perl.

So, problem solved. Thanks for your help.

same problem here