http://www.perlmonks.org?node_id=1012316


in reply to What modules are shipped with ActivePerl on Windows in the default installation?

Why not give them a batch file that 'ppm install's all the modules you might need?

The first call will take a while to update the packlists regardless of whether it downloads or not, and any call that needs to download and install something will take a while... But the rest of the calls for things already installed return quite quickly, so you can just include everything you use in the batch file and it won't be too slow.

C:\>ppm install opengl Downloading ActiveState Package Repository packlist...done Updating ActiveState Package Repository database...done Downloading trouchelle.com packlist...not modified Downloading Bribes packlist...not modified No missing packages to install C:\>ppm install yaml::tiny Downloading YAML-Tiny-1.51...done Unpacking YAML-Tiny-1.51...done Generating HTML for YAML-Tiny-1.51...done Updating files in site area...done 2 files installed C:\>ppm install yaml::tiny No missing packages to install
  • Comment on Re: What modules are shipped with ActivePerl on Windows in the default installation?
  • Download Code

Replies are listed 'Best First'.
Re^2: What modules are shipped with ActivePerl on Windows in the default installation?
by ambrus (Abbot) on Jan 08, 2013 at 21:06 UTC

    I didn't do this because it turned out that the particular script I distributed doesn't need any modules other than Term::ReadKey and that was packed with ActivePerl. (It's a very simple script, mind you.) If there was at least one dependency that's not distributed with ActivePerl, then yes, I should probably list all the dependencies in such an install script.