Yes, what I called "stock perl" is the Perl that comes with your installation of Linux.
In my opinion, you shouldn't remove whatever you copied, because the risk of you removing too much is high.
If you plan on running the application with the stock Perl at the customer's site as well, it's good to test it locally first. This still doesn't make it really convenient because the customer might choose to upgrade the OS and then the stock Perl will get upgraded without you getting further notice.
The package manager of your Linux distribution is documented in the documentation of your Linux distribution. While Perl is widespread and some distribution package managers are written in Perl, Perl has little involvement with Linux distributions and thus does not document Linux distribution package managers. A good package manager automatically includes all dependent modules, but I don't know whether that's the case for RedHat.
In my first response, I listed the approaches in order of descending quality.
You can only find out that you have installed all the required modules if your application runs flawlessly.
In reply to Re^3: Issue in migration of Perl code from 5.6.1 to 5.8.6
by Corion
in thread Issue in migration of Perl code from 5.6.1 to 5.8.6
by ja3
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |