On Tue, Nov 22, 2011 at 7:07 PM, <[email protected]> wrote: > I would like to use the > toolkit to create a .par file with all modules my current script uses and > distribute that among my team to maintain strict module version control and > reduce perl distribution variation (i.e. several people on the team use > ActiveState or Strawberry for Windows whilst others use their native > Unix/Linux version).
I'm not sure if PAR is the right tool in this scenario. It should work as follows: (1) every team member must already have PAR itself (and its dependencies) installed (on the OS/distro of his choice) (2) you pack your script and its non-core dependencies with pp -o foo.par -p myscript.pl then distribute foo.par (3) users can now run the script with perl -MPAR foo.par You have to repeat (2) if you modify your script or add a dependency or update any of the dependent modules. If your team members are using different OS platforms and any of the script's dependencies are not pure-Perl modules then it gets more complicated. You must then create a "multi-arch" .par by repeating (2) on every target platform, adding option "-m" and every time copy over the previously generated foo.par which grows to collect modules for any target platform. Rather unwieldy. You might also look into PAR::Dist. If your "user base" is known in advance and you can directly communicate with it (as suggested by "my team members") I would recommend against the above approach and suggest to use a VCS to distribute both your script and its dependencies. Cheers, Roderich
