I installed a configured Perl 5.32.1 project on a WIN 10 system using the ‘state deploy’ command. I found that I could not run a script in the path, like x.pl, by simply typing x in a command window. I added .PL to PATHEXT. I then realized that .pl was not associated with any program, so I associated it with the perl.exe in the installation directory. Now a script can be found in the path and run, but there are no command line arguments passed to the script ARGV is empty. If I run perl x.pl arg1 arg2, it works fine.
Is it intended that current versions of Perl can run scripts in the path as the older versions before the state tool could? Should this be set up by the deploy command? Has anyone seen and solved this problem?
Other than this, I found that I can easily configure a Perl project, select needed packages using the state command, and deploy. This solves the loss of ppm plus opens up most of CPAN to Windows systems.