in reply to How do you distribute your Perl application to your customers?

I would like to know your way of distributing your Perl application to your customers without using par and pp.
Be there, done that (although not on Windows, but on Solaris in an era Perl wasn't distributed with it). I just compiled a perl, stuck it in the tarball of the rest of the application, and made sure the appropriate use lib calls were done before using anything. Clients could install the tarball anywhere - an environment variable was used to point to the top directory of the tarball install.
  • Comment on Re: How do you distribute your Perl application to your customers?
  • Download Code

Replies are listed 'Best First'.
Re^2: How do you distribute your Perl application to your customers?
by kg (Acolyte) on Jan 11, 2010 at 14:22 UTC
    This sounds like you enjoyed it a lot! :-) This is exactly what I thought about before running across PAR::Packer. What did you do with the additional non-core modules? Did you tarball them too? Thanks!
[reply]
      I didn't need any non-core modules, but if I had, and gotten permission to distribute them, it would have trivial to put them in them somewhere in the tarball. (tarball we distributed then was several hundreds of Mb large, far larger than a perl distro at that time).

      There wasn't much enjoyment though - it was just work.

[reply]
        Sorry, I tried to be ironic - I think it is hard work - and must have been much more when you worked on it. How did you scan the dependencies?
[reply]

In Section Seekers of Perl Wisdom