in reply to Re^2: Installing Perl Modules
in thread Installing Perl Modules

You may not understand that the Active State .ppd file has everything needed for the installation. It is pre-compiled and "ready to go" .

No, .ppd is just xml file that says whats available for download... .ppmx is a zip file containing a .ppd and one module distribution, see http://docs.activestate.com/activeperl/5.16/faq/ActivePerl-faq2.html#ppmx_files

Replies are listed 'Best First'.
Re^4: Installing Perl Modules
by Marshall (Canon) on Aug 29, 2016 at 23:19 UTC
    Your link is similar as the one I posted. Good info about what files it needs! My machine is connected to the internet so this .ppd XML file worked. I would add that the XML .ppd file does contain the dependencies.

    my link had:
    http://docs.activestate.com/activeperl/5.16/faq/ActivePerl-faq2.html
    your link has:
    http://docs.activestate.com/activeperl/5.16/faq/ActivePerl-faq2.html#ppmx_files

    fair enough.

    Update: The reason that my downloaded .ppd files worked is that my machine can access the internet and I can "get the .ppd payload". I have successfully "cloned" an Active State installation from one machine to another by copying my main AS dir to the other machine with the same AS version (given a base installation of the same AS version). However, there is a lot that can go wrong with this idea. I do NOT recommend that idea. Certainly not in a corporate environment.

    I forget the exact syntax right now, but there is a way to have AS dump a file with descriptions of "modules that need to be installed" and that can be used to "clone" your installation. This is the preferred way to "clone" an installation on another machine that doesn't violate any copyrights, etc. And you get the latest versions. I have successfully done that with another user before.