How do I install Perl script dependencies?

Question

I have several scripts that I supply to users as tools for their engineering projects. These scripts contain a lot of duplicated code. I want to extract this code and maintain it in a set of modules. However, in order for this to work, the users would have to install these modules. I don't want to have to tell my users to "make install", etc., as I'm sure none of them would have the patience for that.

I understand that one option is to package everything together with PAR, but ideally the user would be able to open up && edit these scripts if they need to, just like they can now. They also need to be able to move them to whatever directory they want, and I don't want them to have to move a bunch of library files as well.

Is it possible to make a double-click file that installs some bundled Perl modules?

Answer 1

If the users are using systems with a packaging system (dpkg, cygwin, etc.), consider using that.

Answer 2

If you don't mind spending some green, one of the better bet is Perl Dev Kit from Activestate.

From their own description of the product,

• Develop and deploy your Perl programs to anyone on any platform with PerlApp's new cross-platform wrapping.
• Deliver code as executables or as Windows Services, ActiveX components, .NET assemblies or in the System Tray.
• Easily create MSI files using Perl code.

Answer 3

yeah package with either PAR or Shipwright (not sure about binaries). Also use scandeps.pl along the way.

Answer 4

I distribute my script as modules, and then use the normal CPAN toolchain to install them. See my articles Scripts as Modules and Automating Script Distributions with scriptdist. Once you have them in a conventional module distribution, you can install them from their current directory with cpan:

 % cpan .   # install from distribution in the current directory

Depending on how complex your situation is, you might want to create a DPAN, which is a private version of CPAN that your CPAN tools can draw from. You put all of your private modules there, point your CPAN tools at it, and everything happens as it does with a real CPAN mirror. You never have to share your work though.