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


in reply to Packaging Perl Programs (is) Painful

Are there any sane packagers for Perl?
Perhaps. But I believe that to be not very interesting for your problem. For deployment internally, you don't want a different package system for each language you are using - most services you're deploying will depend on components written in different languages anyway.

Use a package system that's suitable for your OS. How do you now distribute something that's not written in Perl? Use whatever you'd be using if you had not know your particular program was written in Perl.

  • Comment on Re: Packaging Perl Programs (is) Painful

Replies are listed 'Best First'.
Re^2: Packaging Perl Programs (is) Painful
by Sue D. Nymme (Monk) on Sep 03, 2010 at 22:49 UTC

    Well, the programs that we develop and use internally that aren't Perl are C or C#, so they are a single executable that we put out onto the network or onto people's computers.

[reply]
      You're using C# without the .NET framework? Are you packaging the entire 20-megabyte .NET 1.0 framework into every executable file (or maybe the 197 MB .NET framework 3.5)?
[reply]

In Section Seekers of Perl Wisdom